Lines Matching refs:be

23 the integer GPIO namespace so that it can be used with the legacy GPIO
24 interface. Each chip must thus have a "base" number (which can be automatically
25 assigned), and for each GPIO the global number will be (base + hardware number).
27 users and thus needs to be maintained.
33 be contiguous; either of those platforms could also use numbers 2000-2063 to
49  - optional base number (will be automatically assigned if omitted)
54 gpio_chip and issue gpiochip_add(). Removing a GPIO controller should be rare;
69 not be required.
83 - spinlock_t should be replaced with raw_spinlock_t [1].
84 - If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
96   handler will be called immediately from the parent irqchip, while
108   RT_FULL: Note, chained IRQ handlers will not be forced threaded on -RT.
109   As result, spinlock_t or any sleepable APIs (like PM runtime) can't be used
111   if required (and if it can't be converted to the nested threaded GPIO irqchip)
112   - chained IRQ handler can be converted to generic irq handler and this way
113   it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT
115   Know W/A: The generic_handle_irq() is expected to be called with IRQ disabled,
116   so IRQ core will complain if it will be called from IRQ handler wich is forced
117   thread. The "fake?" raw lock can be used to W/A this problem:
136   RT_FULL: Such kind of handlers will be forced threaded on -RT, as result IRQ
138   the same W/A as for "CHAINED GPIO irqchips" can be applied.
143   traffic which may in turn incur other IRQs to happen, cannot be handled
159 some helpers that can be enabled by selecting the GPIOLIB_IRQCHIP Kconfig
177   the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
182   expected for GPIO driver that irqchip .set_type() callback have to be called
193 certain GPIO line and should not be relied upon to have been called before
209 Input GPIOs can be used as IRQ signals. When this happens, a driver is requested
220 typically be called in the .startup() and .shutdown() callbacks from the
226 Any provider of irqchips needs to be carefully tailored to support Real Time
235   If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
263 Descriptors requested with gpiochip_request_own_desc() must be released with
266 These functions must be used with care since they do not affect module use