Lines Matching refs:carrier

5 registered by the carrier driver. For example, the PCI driver for the
8 do exactly the same for the VME carrier (actually, it should do it
16 (actually, the carrier driver may choose whether or not to return it -
35              struct fmc_operations *op;      /* carrier-provided */
46              int nr_slots;                   /* Number of slots in this carrier */
59 The following fields must be filled by the carrier driver before
78    * carrier_data: a unique pointer for the carrier.
91 Please note that the carrier should read its own EEPROM memory before
122 As I write this, she SPEC carrier is already completely functional in
129 The carrier provides a number of methods by means of the
154      carrier offers. They are not expected to fail, and most of the time
156      carrier provides a fpga_base pointer, the driver may use direct
178      The carrier enumerates FMC devices by loading a standard (or
181      name argument is NULL, the carrier should reprogram the golden
183      parameters (in a carrier-specific way) the file loaded will match
192      Interrupt management is carrier-specific, so it is abstracted as
201      The method allows to configure a GPIO pin in the carrier, and read
208      called before reprogramming and the carrier should refuse them
213      methods: for example the SPEC driver may define that its carrier
216      same address space is carrier-specific and should only be used
227 While the general idea of a carrier-independent driver seems to fly,
228 configuration of specific signals within the carrier needs at least
229 some knowledge of the carrier itself.  For this reason, the specific
230 driver can request to configure carrier-specific GPIO pins, numbered
238                 int _gpio;      /* internal use by the carrier */
249 yet-unsupported carrier.
254 it most likely means that the current carrier is a still-unknown one.
268 unspecified (NULL). Each carrier is responsible for providing a mapping
269 between virtual and physical GPIO numbers. The carrier may then use the
279 for FMC_GPIO_LED(0) and FMC_GPIO_TP(0). Each carrier will provide
281 the order used by the specific carrier driver in assigning leds and
282 testpoints, so to make a carrier-dependent use of the diagnostic tools.
289 should be carrier-independent and thus use IRQ(0) as a first bet -
290 actually, the knowledge that IRQ0 may fail is carrier-dependent
296    * If no pin in the array can be used by the carrier, `-ENODEV'.
305 allows configuration, input and output with a single carrier operation.