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
184 platforms can read the value of output pins; those that can't should always
200 or SPI.  Commands to read or write those GPIO values require waiting to
220 a threaded IRQ handler, and those accessors must be used instead of
293 configured prior to gpio_request() being called for those GPIOs, e.g. using
393 Those return either the corresponding number in the other namespace, or
492 to route a given GPIO to any one of several pins.  (Yes, those examples all
569 Trivial implementations of those functions can directly use framework
576 Fancier implementations could instead define those as inline functions with
580 optimization is not possible those calls must delegate to the framework
585 for each bank of on-chip GPIOs.  Those GPIOs should be numbered/labeled to
610 board specific code; those board specific callbacks would register devices
637 GPIO tasks:  "leds-gpio" and "gpio_keys", respectively.  Use those
725 what purposes.  However, those numbers are not always stable; GPIOs on