Lines Matching refs:may

37     cases (to support bidirectional signaling).  GPIO controllers may have
41     sometimes level triggered.  Such IRQs may be configurable as system
61 glue logic that may even change between board revisions, and can't ever be
113 may use this predicate:
117 A number that's not valid will be rejected by calls which may request
118 or free GPIOs (see below).  Other numbers may also be rejected; for
195 GPIO access that may sleep
217 Accessing such GPIOs requires a context which may sleep,  for example
226 from contexts which may sleep, since they may need to access the GPIO
248 	 * non-null labels may be useful for diagnostics.
262 are actually in use as GPIOs, for better diagnostics; systems may have
270 Some platforms may also use knowledge about what GPIOs are active for
275 be informed of their use; a gpiolib driver's .request() operation may call
276 pinctrl_request_gpio(), and a gpiolib driver's .free() operation may call
289 Similarly, other aspects of the GPIO or pin may need to be configured, such as
465 gpio (under gpiolib) is still maintained by gpio drivers. It may happen
504 Hardware may support reading or writing GPIOs in gangs, but that's usually
533  - flag saying whether calls to its methods may sleep
537 There is also per-instance data, which may come from device.platform_data:
561 It may also provide a custom value for ARCH_NR_GPIOS, so that it better
593 may well start at zero and go up to a platform-specific limit.  Such GPIOs
613 becomes available.  That may mean the device should not be registered until
623 Platforms which use the "gpiolib" implementors framework may choose to
632 may need to temporarily remove that protection, first importing a GPIO,
664     	"export" ... Userspace may ask the kernel to export control of
680 	"direction" ... reads as either "in" or "out".  This value may
683 		operation, values "low" and "high" may be written to
692 		is configured as an output, this value may be written;
734 or other cards in the stack.  In such cases, you may need to use the
754 After a kernel driver requests a GPIO, it may only be made available in
756 signal direction may change.  This helps drivers prevent userspace code