Lines Matching refs:irqchip
264 It is legal for any IRQ consumer to request an IRQ from any irqchip even if it
283 interrupt controller. This is modeled by an irqchip that will inspect bits
284 inside the GPIO controller to figure out which line fired it. The irqchip
299 spinlock_t or any sleepable APIs (like PM runtime) as part of its irqchip
305 on an irqchip. Create the callbacks if needed.[2]
316 system interrupt controller. This means that the GPIO irqchip handler will
317 be called immediately from the parent irqchip, while holding the IRQs
318 disabled. The GPIO irqchip will then end up calling something like this
334 If required (and if it can't be converted to the nested threaded GPIO irqchip,
354 The GPIO irqchip will then end up calling something like this sequence in
367 other GPIO irqchip residing on the other side of a sleeping bus such as I2C
458 * Statically populate the irqchip. Note that it is made const
532 * Statically populate the irqchip. Note that it is made const
574 /* Typical state container with dynamic irqchip */
612 * Statically populate the irqchip. Note that it is made const
660 the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
663 - Nominally set gpio_irq_chip.handler to handle_bad_irq. Then, if your irqchip
665 in the irqchip .set_type() callback depending on what your controller
690 When implementing an irqchip inside a GPIO driver, these two functions should
692 irqchip.
694 When using the gpiolib irqchip helpers, these callbacks are automatically
708 the irqchip driver should call::
717 When implementing an irqchip inside a GPIO driver, these two functions should
719 irqchip.
721 When IRQCHIP_IMMUTABLE is not advertised by the irqchip, these callbacks