Lines Matching refs:an

26 With the descriptor-based interface, GPIOs are identified with an opaque,
36 device that displays digits), an additional index argument can be specified:
54 Both functions return either a valid GPIO descriptor, or an error code checkable
57 other error codes are used for cases where a GPIO has been assigned but an error
59 errors and an absence of GPIO for optional GPIO parameters. For the common
79 This function returns a struct gpio_descs which contains an array of
125 For an array of GPIOs this function can be used:
131 from an array acquired with gpiod_get_array().
178 Use the following calls to access GPIOs from an atomic context:
184 of an output pin, the value returned should be what's seen on the pin. That
192 (see below) is an error.
257 As an example, if the active-low property for a dedicated GPIO is set, and the
278 The following functions set the output values of an array of GPIOs:
293 The array can be an arbitrary set of GPIOs. The functions will try to set
301 	* desc_array	- an array of GPIO descriptors
302 	* value_array	- an array of values to assign to the GPIOs
329 It will return an IRQ number, or a negative errno code if the mapping can't be
330 done (most likely because that particular GPIO cannot be used as IRQ). It is an
331 unchecked error to use a GPIO that wasn't set up as an input using
332 gpiod_direction_input(), or to use an IRQ number that didn't originally come
347 connection IDs (names) for GPIOs, so it is necessary to use an additional
375 Freeing a GPIO obtained by one API with the other API is forbidden and an