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
418   /* Typical state container with dynamic irqchip */
428   /* Set up the irqchip dynamically */
453   /* Typical state container with dynamic irqchip */
464   /* Set up the irqchip dynamically */
492 - DEPRECATED: gpiochip_irqchip_add(): adds a chained cascaded irqchip to a
498 - gpiochip_irqchip_add_nested(): adds a nested cascaded irqchip to a gpiochip,
501   Apart from that it works exactly like the chained irqchip.
506   irqchip data is likely used by the parent irqchip.
524   the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
529   expected for GPIO driver that irqchip .set_type() callback will be called
531   handle_level_irq() and/or handle_edge_irq() in the irqchip .set_type()
557 When implementing an irqchip inside a GPIO driver, these two functions should
559 irqchip.
561 When using the gpiolib irqchip helpers, these callbacks are automatically
575 the irqchip driver should call::
584 When implementing an irqchip inside a GPIO driver, these two functions should
586 irqchip.
588 When using the gpiolib irqchip helpers, these callbacks are automatically