Lines Matching refs:may
16 (actually, the carrier driver may choose whether or not to return it -
21 Please note that all the machinery is in place but some details may
37 int eeprom_len; /* Usually 8kB, may be less */
68 * irq: number for the mezzanine; may be zero.
80 * fpga_base: the I/O memory address (may be NULL).
118 Note: mezzanine_data may be redundant, because Linux offers the drvdata
119 approach, so the field may be removed in later versions of this bus
156 carrier provides a fpga_base pointer, the driver may use direct
197 but fmc-specific flags may be added in the future. You'll most
211 reserved to fit bigger I2C devices in the future. Carriers may
213 methods: for example the SPEC driver may define that its carrier
243 By specifying a carrier_name for each pin, the driver may access
252 the SPEC and the SVEC may request configuration of two different GPIO
269 between virtual and physical GPIO numbers. The carrier may then use the
278 scope probe to be plugged at some point during development) it may ask
290 actually, the knowledge that IRQ0 may fail is carrier-dependent