Lines Matching refs:using
52 If a function is implemented by using several GPIOs together (e.g. a simple LED
109 For a function using multiple GPIOs all of those can be obtained with one call::
159 A GPIO descriptor can be disposed of using the gpiod_put() function::
168 It is also not allowed to individually release descriptors (using gpiod_put())
205 Be aware that there is no default direction for GPIOs. Therefore, **using a GPIO
229 Also, using these calls for GPIOs that can't safely be accessed without sleeping
235 Some GPIO controllers must be accessed using message based buses like I2C or
297 It is possible to override these semantics using the set_raw/get_raw functions
318 The active low state of a GPIO can also be queried and toggled using the
380 The descriptor array can be obtained using the gpiod_get_array() function
382 matches the desired group of GPIOs, those GPIOs can be accessed by simply using
390 descriptors may be obtained using any combination of gpiod_get() and
415 corresponding to a given GPIO using the following call::
421 unchecked error to use a GPIO that wasn't set up as an input using
452 Many kernel subsystems and drivers still handle GPIOs using the legacy
464 acquired using e.g. gpio_request_one(), and the returned GPIO descriptor is only
465 considered valid until that GPIO number is released using gpio_free().