Lines Matching refs:that

4 This document describes the consumer interface of the GPIO framework. Note that
12 Drivers that can't work without standard GPIO calls should have Kconfig entries
13 that depend on GPIOLIB. The functions that allow a driver to obtain and use
18 All the functions that work with the descriptor-based GPIO interface are
27 non-forgeable handler that must be obtained through a call to one of the
29 device that will use the GPIO and the function the requested GPIO is supposed to
36 device that displays digits), an additional index argument can be specified:
164 Be aware that there is no default direction for GPIOs. Therefore, **using a GPIO
186 reported earlier from gpiod_direction_*(). However, note that not all platforms
187 can read the value of output pins; those that can't should always return zero.
188 Also, using these calls for GPIOs that can't safely be accessed without sleeping
199 Platforms that support this type of GPIO distinguish them from other GPIOs by
213 Other than the fact that these accessors might sleep, and will work on GPIOs
214 that can't be accessed from hardIRQ handlers, these calls act the same as the
236 Note that these functions should only be used with great moderation ; a driver
259 corresponding chip driver. In that case a significantly improved performance
269 or one of its variants. If the group of descriptors returned by that function
282 Note that for optimal performance GPIOs belonging to the same chip should be
294 done (most likely because that particular GPIO cannot be used as IRQ). It is an
295 unchecked error to use a GPIO that wasn't set up as an input using
296 gpiod_direction_input(), or to use an IRQ number that didn't originally come
301 by the board-specific initialization code. Note that IRQ trigger options are
316 GPIOs described by the GpioIo()/GpioInt() resources in _CRS.  If that is the