Lines Matching refs:functions
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
28 gpiod_get() functions. Like many other kernel subsystems, gpiod_get() takes the
49 later with one of the dedicated functions.
54 Both functions return either a valid GPIO descriptor, or an error code checkable
61 gpiod_get_index_optional() functions can be used. These functions return NULL
94 Device-managed variants of these functions are also defined:
129 It is strictly forbidden to use a descriptor after calling these functions.
147 invoking one of the gpiod_direction_*() functions:
239 Note that these functions should only be used with great moderation ; a driver
247 gpiod_set_value_xxx() or gpiod_set_array_value_xxx() functions operate with
253 With this, all the gpiod_set_(array)_value_xxx() functions interpret the
271 Please note again that the set_raw/get_raw functions should be avoided as much
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
299 The gpiod_set_array() functions take three arguments:
364 descriptor-based API, the following two functions allow you to convert a GPIO