Lines Matching refs:can

12 Drivers that can't work without standard GPIO calls should have Kconfig entries
36 device that displays digits), an additional index argument can be specified:
43 for the GPIO. Values can be:
58 gpiod_get_index_optional() functions can be used. These functions return NULL
70 For a function using multiple GPIOs all of those can be obtained with one call:
118 A GPIO descriptor can be disposed of using the gpiod_put() function:
122 For an array of GPIOs this function can be used:
158 A driver can also query the current direction of a GPIO:
171 Most GPIO controllers can be accessed with memory read/write instructions. Those
172 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
187 can read the value of output pins; those that can't should always return zero.
188 Also, using these calls for GPIOs that can't safely be accessed without sleeping
197 sleeping, which can't be done from inside IRQ handlers.
214 that can't be accessed from hardIRQ handlers, these calls act the same as the
232 The active-low state of a GPIO can also be queried using the following call:
257 The array can be an arbitrary set of GPIOs. The functions will try to set
260 can be expected. If simultaneous setting is not possible the GPIOs will be set
268 The descriptor array can be obtained using the gpiod_get_array() function
270 matches the desired group of GPIOs, those GPIOs can be set by simply using
280 manually before it can be used with gpiod_set_array().
288 GPIO lines can quite often be used as IRQs. You can get the IRQ number
293 It will return an IRQ number, or an negative errno code if the mapping can't be
299 Non-error values returned from gpiod_to_irq() can be passed to request_irq() or
334 The GPIO number returned by desc_to_gpio() can be safely used as long as the