Lines Matching refs:t
13 Drivers that can't work without standard GPIO calls should have Kconfig entries
191 checked, since the get/set calls don't return errors and since misconfiguration
213 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
223 won't always match the specified output value, because of issues including
228 can read the value of output pins; those that can't should always return zero.
229 Also, using these calls for GPIOs that can't safely be accessed without sleeping
238 sleeping, which can't be done from inside IRQ handlers.
255 that can't be accessed from hardIRQ handlers, these calls act the same as the
286 gpiod_set_raw_value(desc, 0); don't care low
287 gpiod_set_raw_value(desc, 1); don't care high
419 It will return an IRQ number, or a negative errno code if the mapping can't be
421 unchecked error to use a GPIO that wasn't set up as an input using
422 gpiod_direction_input(), or to use an IRQ number that didn't originally come