Lines Matching full:those

49   - Most GPIOs can be accessed while holding spinlocks, but those accessed
99 Platforms define how they use those integers, and usually #define symbols
109 The numbers need not be contiguous; either of those platforms could also
165 Those don't need to sleep, and can safely be done from inside hard
183 platforms can read the value of output pins; those that can't should always
199 or SPI.  Commands to read or write those GPIO values require waiting to
211 a threaded IRQ handler, and those accessors must be used instead of
282 configured prior to gpio_request() being called for those GPIOs, e.g. using
360 Those return either the corresponding number in the other namespace, or
454 to route a given GPIO to any one of several pins.  (Yes, those examples all
526 Trivial implementations of those functions can directly use framework
532 Fancier implementations could instead define those as inline functions with
536 optimization is not possible those calls must delegate to the framework
541 for each bank of on-chip GPIOs.  Those GPIOs should be numbered/labeled to
566 board specific code; those board specific callbacks would register devices
593 GPIO tasks:  "leds-gpio" and "gpio_keys", respectively.  Use those
681 what purposes.  However, those numbers are not always stable; GPIOs on