Lines Matching +full:enum +full:- +full:as +full:- +full:flags
21 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
25 - Truly optional GPIOLIB support - where the driver does not really make use
26 of the GPIOs on certain compile-time configurations for certain systems, but
27 will use it under other compile-time configurations. In this case the
29 be met with console warnings that may be perceived as intimidating.
35 All the functions that work with the descriptor-based GPIO interface are
45 With the descriptor-based interface, GPIOs are identified with an opaque,
46 non-forgeable handler that must be obtained through a call to one of the
52 enum gpiod_flags flags)
59 enum gpiod_flags flags)
62 see Documentation/driver-api/gpio/board.rst
64 The flags parameter is used to optionally specify a direction and initial value
69 * GPIOD_IN to initialize the GPIO as input.
70 * GPIOD_OUT_LOW to initialize the GPIO as output with a value of 0.
71 * GPIOD_OUT_HIGH to initialize the GPIO as output with a value of 1.
72 * GPIOD_OUT_LOW_OPEN_DRAIN same as GPIOD_OUT_LOW but also enforce the line
74 * GPIOD_OUT_HIGH_OPEN_DRAIN same as GPIOD_OUT_HIGH but also enforce the line
81 The two last flags are used for use cases where open drain is mandatory, such
82 as I2C: if the line is not already configured as open drain in the mappings
87 with IS_ERR() (they will never return a NULL pointer). -ENOENT will be returned
94 instead of -ENOENT if no GPIO has been assigned to the requested function::
98 enum gpiod_flags flags)
103 enum gpiod_flags flags)
108 -ENOSYS return codes. System integrators should however be careful to enable
115 enum gpiod_flags flags)
127 The following function returns NULL instead of -ENOENT if no GPIOs have been
132 enum gpiod_flags flags)
134 Device-managed variants of these functions are also defined::
137 enum gpiod_flags flags)
142 enum gpiod_flags flags)
146 enum gpiod_flags flags)
151 enum gpiod_flags flags)
155 enum gpiod_flags flags)
159 enum gpiod_flags flags)
173 The device-managed variants are, unsurprisingly::
184 -----------------
186 direction-setting flags have been given to gpiod_get*(), this is done by
195 for spinlock-safe GPIOs it is OK to use them before tasking is enabled, as part
212 Spinlock-Safe GPIO Access
213 -------------------------
215 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
226 open-drain signaling and output latencies.
236 --------------------------
253 IRQ handler, and those accessors must be used instead of spinlock-safe
257 that can't be accessed from hardIRQ handlers, these calls act the same as the
258 spinlock-safe calls.
264 ---------------------------------------
265 As a consumer should not have to care about the physical line level, all of the
278 parameter "value" as "active" ("1") or "inactive" ("0"). The physical line
281 As an example, if the active low property for a dedicated GPIO is set, and the
300 but it should be avoided as much as possible, especially by system-agnostic drivers
306 -------------------------
311 The following set of calls ignore the active-low or open drain property of a GPIO and
331 -------------------------------------------------
376 * array_size - the number of array elements
377 * desc_array - an array of GPIO descriptors
378 * array_info - optional information obtained from gpiod_get_array()
379 * value_bitmap - a bitmap to store the GPIOs' values (get) or
388 gpiod_set_array_value(my_gpio_descs->ndescs, my_gpio_descs->desc,
389 my_gpio_descs->info, my_gpio_value_bitmap);
406 banks as data I/O ports without much loss of performance.
411 values are stored in value_array rather than passed back as return value.
415 --------------------
416 GPIO lines can quite often be used as IRQs. You can get the IRQ number
422 done (most likely because that particular GPIO cannot be used as IRQ). It is an
423 unchecked error to use a GPIO that wasn't set up as an input using
427 Non-error values returned from gpiod_to_irq() can be passed to request_irq() or
429 by the board-specific initialization code. Note that IRQ trigger options are
430 part of the IRQ interface, e.g. IRQF_TRIGGER_FALLING, as are system wakeup
449 For details refer to Documentation/firmware-guide/acpi/gpio-properties.rst
455 integer-based interface. It is strongly recommended to update these to the new
458 and vice-versa::
463 The GPIO number returned by desc_to_gpio() can safely be used as a parameter of
464 the gpio\_*() functions for as long as the GPIO descriptor `desc` is not freed.