Lines Matching +full:line +full:- +full:based
6 it describes the new descriptor-based interface. For a description of the
7 deprecated integer-based GPIO interface please refer to legacy.rst.
23 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
27 - Truly optional GPIOLIB support - where the driver does not really make use
28 of the GPIOs on certain compile-time configurations for certain systems, but
29 will use it under other compile-time configurations. In this case the
33 All the functions that work with the descriptor-based GPIO interface are
43 With the descriptor-based interface, GPIOs are identified with an opaque,
44 non-forgeable handler that must be obtained through a call to one of the
60 see Documentation/driver-api/gpio/board.rst
70 * GPIOD_OUT_LOW_OPEN_DRAIN same as GPIOD_OUT_LOW but also enforce the line
72 * GPIOD_OUT_HIGH_OPEN_DRAIN same as GPIOD_OUT_HIGH but also enforce the line
75 Note that the initial value is *logical* and the physical line level depends on
76 whether the line is configured active high or active low (see
80 as I2C: if the line is not already configured as open drain in the mappings
85 with IS_ERR() (they will never return a NULL pointer). -ENOENT will be returned
92 instead of -ENOENT if no GPIO has been assigned to the requested function::
106 -ENOSYS return codes. System integrators should however be careful to enable
125 The following function returns NULL instead of -ENOENT if no GPIOs have been
132 Device-managed variants of these functions are also defined::
171 The device-managed variants are, unsurprisingly::
182 -----------------
184 direction-setting flags have been given to gpiod_get*(), this is done by
193 for spinlock-safe GPIOs it is OK to use them before tasking is enabled, as part
210 Spinlock-Safe GPIO Access
211 -------------------------
213 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
224 open-drain signaling and output latencies.
234 --------------------------
235 Some GPIO controllers must be accessed using message based buses like I2C or
251 IRQ handler, and those accessors must be used instead of spinlock-safe
256 spinlock-safe calls.
262 ---------------------------------------
263 As a consumer should not have to care about the physical line level, all of the
267 and if so, they manipulate the passed value before the physical line level is
276 parameter "value" as "asserted" ("1") or "de-asserted" ("0"). The physical line
280 gpiod_set_(array)_value_xxx() passes "asserted" ("1"), the physical line level
285 Function (example) line property physical line
298 but it should be avoided as much as possible, especially by system-agnostic drivers
299 which should not need to care about the actual physical line level and worry about
304 -------------------------
305 Consumers exist that need to manage the logical state of a GPIO line, i.e. the value
307 line.
309 The following set of calls ignore the active-low or open drain property of a GPIO and
310 work on the raw line value::
325 should not have to care about the physical line level or open drain semantics.
329 -------------------------------------------------
374 * array_size - the number of array elements
375 * desc_array - an array of GPIO descriptors
376 * array_info - optional information obtained from gpiod_get_array()
377 * value_bitmap - a bitmap to store the GPIOs' values (get) or
386 gpiod_set_array_value(my_gpio_descs->ndescs, my_gpio_descs->desc,
387 my_gpio_descs->info, my_gpio_value_bitmap);
413 --------------------
425 Non-error values returned from gpiod_to_irq() can be passed to request_irq() or
427 by the board-specific initialization code. Note that IRQ trigger options are
447 For details refer to Documentation/firmware-guide/acpi/gpio-properties.rst
453 integer-based interface. It is strongly recommended to update these to the new
456 and vice-versa::