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
424 /* Typical state container with dynamic irqchip */
434 /* Set up the irqchip dynamically */
461 /* Typical state container with dynamic irqchip */
471 /* Set up the irqchip dynamically */
500 /* Typical state container with dynamic irqchip */
511 /* Set up the irqchip dynamically */
547 the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
550 - Nominally set gpio_irq_chip.handler to handle_bad_irq. Then, if your irqchip
552 in the irqchip .set_type() callback depending on what your controller
577 When implementing an irqchip inside a GPIO driver, these two functions should
579 irqchip.
581 When using the gpiolib irqchip helpers, these callbacks are automatically
595 the irqchip driver should call::
604 When implementing an irqchip inside a GPIO driver, these two functions should
606 irqchip.
608 When using the gpiolib irqchip helpers, these callbacks are automatically