Lines Matching refs:irqchip
265 It is legal for any IRQ consumer to request an IRQ from any irqchip even if it
284 interrupt controller. This is modeled by an irqchip that will inspect bits
285 inside the GPIO controller to figure out which line fired it. The irqchip
300 spinlock_t or any sleepable APIs (like PM runtime) as part of its irqchip
306 on an irqchip. Create the callbacks if needed.[2]
317 system interrupt controller. This means that the GPIO irqchip handler will
318 be called immediately from the parent irqchip, while holding the IRQs
319 disabled. The GPIO irqchip will then end up calling something like this
335 If required (and if it can't be converted to the nested threaded GPIO irqchip,
355 The GPIO irqchip will then end up calling something like this sequence in
368 other GPIO irqchip residing on the other side of a sleeping bus such as I2C
459 * Statically populate the irqchip. Note that it is made const
533 * Statically populate the irqchip. Note that it is made const
575 /* Typical state container with dynamic irqchip */
613 * Statically populate the irqchip. Note that it is made const
661 the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
664 - Nominally set gpio_irq_chip.handler to handle_bad_irq. Then, if your irqchip
666 in the irqchip .set_type() callback depending on what your controller
691 When implementing an irqchip inside a GPIO driver, these two functions should
693 irqchip.
695 When using the gpiolib irqchip helpers, these callbacks are automatically
709 the irqchip driver should call::
718 When implementing an irqchip inside a GPIO driver, these two functions should
720 irqchip.
722 When IRQCHIP_IMMUTABLE is not advertised by the irqchip, these callbacks