Lines Matching refs:calls

5 These calls use the gpio_* naming prefix.  No other calls should use that
77 standard GPIO calls should have Kconfig entries which depend on GPIOLIB.  The
78 GPIO calls are available, either as "real code" or as optimized-away stubs,
117 A number that's not valid will be rejected by calls which may request
139 be checked, since the get/set calls don't have error returns and since
140 misconfiguration is possible.  You should normally issue these calls from
166 Use the following calls to access such GPIOs,
180 The get/set calls have no error returns because "invalid GPIO" should have
183 return zero.  Also, using these calls for GPIOs that can't safely be accessed
187 calls to access the GPIO value in cases where the GPIO number (and for
190 and not to need spinlocks.  Such optimized calls can make bitbanging
192 dozens of instructions on subroutine calls.
222 on GPIOs that can't be accessed from hardIRQ handlers, these calls act
223 the same as the spinlock-safe calls.
225   ** IN ADDITION ** calls to setup and configure such GPIOs must be made
227 controller chip too:  (These setup calls are usually made from board
245 To help catch system configuration errors, two calls are defined.
257 gpio_request() must be checked.  You should normally issue these calls from
261 These calls serve two basic purposes.  One is marking the signals which
299 are claimed, three additional calls are defined:
383 map between them using calls like:
397 These two mapping calls are expected to cost on the order of a single
533  - flag saying whether calls to its methods may sleep
586 optimization is not possible those calls must delegate to the framework
614 calls for that GPIO can work.  One way to address such dependencies is for