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,
182 The get/set calls have no error returns because "invalid GPIO" should have
185 return zero.  Also, using these calls for GPIOs that can't safely be accessed
189 calls to access the GPIO value in cases where the GPIO number (and for
192 and not to need spinlocks.  Such optimized calls can make bitbanging
194 dozens of instructions on subroutine calls.
224 on GPIOs that can't be accessed from hardIRQ handlers, these calls act
225 the same as the spinlock-safe calls.
227 **IN ADDITION** calls to setup and configure such GPIOs must be made
229 controller chip too  (These setup calls are usually made from board
247 To help catch system configuration errors, two calls are defined::
259 gpio_request() must be checked.  You should normally issue these calls from
263 These calls serve two basic purposes.  One is marking the signals which
301 are claimed, three additional calls are defined::
385 map between them using calls like::
399 These two mapping calls are expected to cost on the order of a single
535  - flag saying whether calls to its methods may sleep
580 optimization is not possible those calls must delegate to the framework
608 calls for that GPIO can work.  One way to address such dependencies is for