Lines Matching refs:irqchip

77 The IRQ portions of the GPIO block are implemented using an irqchip, using
86   on an irqchip. Create the callbacks if needed [2].
93   system interrupt controller. This means the GPIO irqchip is registered
95   gpiochip_set_chained_irqchip() helper function, and the GPIO irqchip
96   handler will be called immediately from the parent irqchip, while
97   holding the IRQs disabled. The GPIO irqchip will then end up calling
111   if required (and if it can't be converted to the nested threaded GPIO irqchip)
129   The GPIO irqchip will then end up calling something like this sequence in
141   other GPIO irqchip residing on the other side of a sleeping bus. Of course
162 * gpiochip_irqchip_add(): adds an irqchip to a gpiochip. It will pass
170   data. (Notice handler data, since the irqchip data is likely used by the
171   parent irqchip!) This is for the chained type of chip. This is also used
172   to set up a nested irqchip if NULL is passed as handler.
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
184   and/or handle_edge_irq() in the irqchip .set_type() callback depending on
187 It is legal for any IRQ consumer to request an IRQ from any irqchip no matter
197 callbacks from the GPIO and irqchip APIs. Do not rely on gpiod_to_irq() having
219 When implementing an irqchip inside a GPIO driver, these two functions should
221 irqchip.