driver-api/gpio/driver.rst

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
423   /* Typical state container with dynamic irqchip */
433   /* Set up the irqchip dynamically */
460   /* Typical state container with dynamic irqchip */
471   /* Set up the irqchip dynamically */
499 - DEPRECATED: gpiochip_irqchip_add(): adds a chained cascaded irqchip to a
505 - gpiochip_irqchip_add_nested(): adds a nested cascaded irqchip to a gpiochip,
508   Apart from that it works exactly like the chained irqchip.
526   the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
531   expected for GPIO driver that irqchip .set_type() callback will be called
533   handle_level_irq() and/or handle_edge_irq() in the irqchip .set_type()
559 When implementing an irqchip inside a GPIO driver, these two functions should
561 irqchip.
563 When using the gpiolib irqchip helpers, these callbacks are automatically
577 the irqchip driver should call::
586 When implementing an irqchip inside a GPIO driver, these two functions should
588 irqchip.
590 When using the gpiolib irqchip helpers, these callbacks are automatically