Lines Matching refs:use

5 These calls use the gpio_* naming prefix.  No other calls should use that
75 use it when possible.  Platforms must select ARCH_REQUIRE_GPIOLIB or
79 when drivers use the include file:
87 use them; drivers don't need to add them explicitly.
97 Platforms define how they use those integers, and usually #define symbols
99 to the relevant schematics.  In contrast, drivers should only use GPIO
108 use numbers 2000-2063 to identify GPIOs in a bank of I2C GPIO expanders.
110 If you want to initialize a structure with an invalid GPIO number, use
113 may use this predicate:
141 a task context.  However, for spinlock-safe GPIOs it's OK to use them
262 are actually in use as GPIOs, for better diagnostics; systems may have
265 (a) two or more drivers wrongly think they have exclusive use of that
267 needed to manage a signal that's in active use.  That is, requesting a
270 Some platforms may also use knowledge about what GPIOs are active for
274 For GPIOs that use pins known to the pinctrl subsystem, that subsystem should
275 be informed of their use; a gpiolib driver's .request() operation may call
382 two logically distinct namespaces (GPIO 0 need not use IRQ 0).  You can
393 some GPIOs can't be used as IRQs.)  It is an unchecked error to use a GPIO
395 to use an IRQ number that didn't originally come from gpio_to_irq().
414 Sometimes shared signals need to use "open drain" signaling, where only the
421 Also, bidirectional data bus signals sometimes use open drain signals.
425 there's a common idiom you can use to emulate it with any GPIO pin that can
488 explicit multiplexing; another might have just two options for use of any
495 or support them in the same way; and any given board might use external
523 this framework, and the state of the GPIOs currently in use.
543 rare; use gpiochip_remove() when it is unavoidable.
550 requested as GPIOs.  They can use gpiochip_is_requested(), which returns
562 reflects the number of GPIOs in actual use on that platform, without
575 Trivial implementations of those functions can directly use framework
603 numbers to use with gpiochip_add().  Their numbers often start right after
623 Platforms which use the "gpiolib" implementors framework may choose to
634 the write protection.  In normal use, GPIO #23 would never be touched,
699 		you use poll(2), set the events POLLPRI and POLLERR. If you
700 		use select(2), set the file descriptor in exceptfds. After
734 or other cards in the stack.  In such cases, you may need to use the
736 the correct GPIO number to use for a given signal.
768 use this to provide the interface under their own device in sysfs with
771 Drivers can use gpio_sysfs_set_active_low() to hide GPIO line polarity