Lines Matching refs:irqchip

217 The IRQ portions of the GPIO block are implemented using an irqchip, using
227   on an irqchip. Create the callbacks if needed [2].
234   system interrupt controller. This means that the GPIO irqchip handler will
235   be called immediately from the parent irqchip, while holding the IRQs
236   disabled. The GPIO irqchip will then end up calling something like this
251   If required (and if it can't be converted to the nested threaded GPIO irqchip)
269   The GPIO irqchip will then end up calling something like this sequence in
281   other GPIO irqchip residing on the other side of a sleeping bus. Of course
302 * gpiochip_irqchip_add(): adds a chained irqchip to a gpiochip. It will pass
308 * gpiochip_irqchip_add_nested(): adds a nested irqchip to a gpiochip.
309   Apart from that it works exactly like the chained irqchip.
313   data. (Notice handler data, since the irqchip data is likely used by the
314   parent irqchip!).
331   the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
336   expected for GPIO driver that irqchip .set_type() callback have to be called
338   and/or handle_edge_irq() in the irqchip .set_type() callback depending on
341 It is legal for any IRQ consumer to request an IRQ from any irqchip no matter
351 callbacks from the GPIO and irqchip APIs. Do not rely on gpiod_to_irq() having
373 When implementing an irqchip inside a GPIO driver, these two functions should
375 irqchip.
377 When using the gpiolib irqchip helpers, these callback are automatically