Lines Matching refs:IRQ

46  - method to return the IRQ number associated to a given GPIO
72 The IRQ portions of the GPIO block are implemented using an irqchip, using
79   an SoC. This means that there is a fast IRQ handler for the GPIOs that
80   gets called in a chain from the parent IRQ handler, most typically the
98   such drivers that need slow bus traffic to read out IRQ status and similar,
100   in a quick IRQ handler with IRQs disabled. Instead they need to spawn a
101   thread and then mask the parent IRQ line until the interrupt is handled
119   the struct gpio_chip* for the chip to all IRQ callbacks, so the callbacks
125   gpio_chip from a parent IRQ and passes the struct gpio_chip* as handler
136 It is legal for any IRQ consumer to request an IRQ from any irqchip no matter
137 if that is a combined GPIO+IRQ driver. The basic premise is that gpio_chip and
141 gpiod_to_irq() is just a convenience function to figure out the IRQ for a
143 the IRQ is used.
156 Locking IRQ usage
158 Input GPIOs can be used as IRQ signals. When this happens, a driver is requested
159 to mark the GPIO as being used as an IRQ:
163 This will prevent the use of non-irq related GPIO APIs until the GPIO IRQ lock