Lines Matching refs:IRQ

46  - method to return the IRQ number associated to a given GPIO
68 on -RT (inside hard IRQ handlers and similar contexts). Normally this should
77 The IRQ portions of the GPIO block are implemented using an irqchip, using
91   an SoC. This means that there is a fast IRQ handler for the GPIOs that
92   gets called in a chain from the parent IRQ handler, most typically the
108   RT_FULL: Note, chained IRQ handlers will not be forced threaded on -RT.
110   in chained IRQ handler.
112   - chained IRQ handler can be converted to generic irq handler and this way
113   it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT
115   Know W/A: The generic_handle_irq() is expected to be called with IRQ disabled,
116   so IRQ core will complain if it will be called from IRQ handler wich is forced
127   but chained IRQ handlers are not used. Instead GPIO IRQs dispatching is
128   performed by generic IRQ handler which is configured using request_irq().
133 	for each detected GPIO IRQ
136   RT_FULL: Such kind of handlers will be forced threaded on -RT, as result IRQ
137   core will complain that generic_handle_irq() is called with IRQ enabled and
142   such drivers that need slow bus traffic to read out IRQ status and similar,
144   in a quick IRQ handler with IRQs disabled. Instead they need to spawn a
145   thread and then mask the parent IRQ line until the interrupt is handled
163   the struct gpio_chip* for the chip to all IRQ callbacks, so the callbacks
169   gpio_chip from a parent IRQ and passes the struct gpio_chip* as handler
183   before using/enabling GPIO IRQ. Then set the handler to handle_level_irq()
187 It is legal for any IRQ consumer to request an IRQ from any irqchip no matter
188 if that is a combined GPIO+IRQ driver. The basic premise is that gpio_chip and
192 gpiod_to_irq() is just a convenience function to figure out the IRQ for a
194 the IRQ is used.
207 Locking IRQ usage
209 Input GPIOs can be used as IRQ signals. When this happens, a driver is requested
210 to mark the GPIO as being used as an IRQ:
214 This will prevent the use of non-irq related GPIO APIs until the GPIO IRQ lock
223 Real-Time compliance for GPIO IRQ chips
238   from chained IRQ handler;
241 - Chained GPIO irqchips: get rid of chained IRQ handler and use generic irq
244   GPIO IRQ chip implementation;