Lines Matching full:calls

7 These calls use the gpio_* naming prefix.  No other calls should use that
79 standard GPIO calls should have Kconfig entries which depend on GPIOLIB.  The
80 GPIO calls are available, either as "real code" or as optimized-away stubs,
119 A number that's not valid will be rejected by calls which may request
141 be checked, since the get/set calls don't have error returns and since
142 misconfiguration is possible.  You should normally issue these calls from
168 Use the following calls to access such GPIOs::
181 The get/set calls have no error returns because "invalid GPIO" should have
184 return zero.  Also, using these calls for GPIOs that can't safely be accessed
188 calls to access the GPIO value in cases where the GPIO number (and for
191 and not to need spinlocks.  Such optimized calls can make bitbanging
193 dozens of instructions on subroutine calls.
215 on GPIOs that can't be accessed from hardIRQ handlers, these calls act
216 the same as the spinlock-safe calls.
218 **IN ADDITION** calls to setup and configure such GPIOs must be made
220 controller chip too  (These setup calls are usually made from board
236 To help catch system configuration errors, two calls are defined::
248 gpio_request() must be checked.  You should normally issue these calls from
252 These calls serve two basic purposes.  One is marking the signals which
290 are claimed, three additional calls are defined::
355 map between them using calls like::
366 These two mapping calls are expected to cost on the order of a single
497  - flag saying whether calls to its methods may sleep
536 optimization is not possible those calls must delegate to the framework
564 calls for that GPIO can work.  One way to address such dependencies is for