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:
46 for the GPIO. Values can be:
61 gpiod_get_index_optional() functions can be used. These functions return NULL
73 For a function using multiple GPIOs all of those can be obtained with one call:
121 A GPIO descriptor can be disposed of using the gpiod_put() function:
125 For an array of GPIOs this function can be used:
161 A driver can also query the current direction of a GPIO:
174 Most GPIO controllers can be accessed with memory read/write instructions. Those
175 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
190 can read the value of output pins; those that can't should always return zero.
191 Also, using these calls for GPIOs that can't safely be accessed without sleeping
200 sleeping, which can't be done from inside IRQ handlers.
217 that can't be accessed from hardIRQ handlers, these calls act the same as the
235 The active-low state of a GPIO can also be queried using the following call:
293 The array can be an arbitrary set of GPIOs. The functions will try to set
296 can be expected. If simultaneous setting is not possible the GPIOs will be set
304 The descriptor array can be obtained using the gpiod_get_array() function
306 matches the desired group of GPIOs, those GPIOs can be set by simply using
316 manually before it can be used with gpiod_set_array().
324 GPIO lines can quite often be used as IRQs. You can get the IRQ number
329 It will return an IRQ number, or a negative errno code if the mapping can't be
335 Non-error values returned from gpiod_to_irq() can be passed to request_irq() or
370 The GPIO number returned by desc_to_gpio() can be safely used as long as the