Lines Matching refs:GPIO

201      The method allows to configure a GPIO pin in the carrier, and read
202      its current value if it is configured as input. See *note The GPIO
221 The GPIO Abstraction
224 Support for GPIO pins in the fmc-bus environment is not very
230 driver can request to configure carrier-specific GPIO pins, numbered
252 the SPEC and the SVEC may request configuration of two different GPIO
256 If, however, your GPIO pin has a specific known role, you can pass a
266 Use of virtual GPIO numbers (anything but FMC_GPIO_RAW) is allowed
269 between virtual and physical GPIO numbers. The carrier may then use the
280 suitable GPIO pins.  Clearly, the person running the drivers will know
298    * If at least one virtual GPIO number cannot be mapped, `-ENOENT'.
306 Given the typical use case of FMC devices, GPIO operations are not
307 expected to ever by in hot paths, and GPIO access so fare has only been
309 reading inputs is not expected to be common. If your device has GPIO
311 GPIO mechanisms.