Lines Matching refs:IRQ
63 - method to return the IRQ number associated to a given GPIO line
87 atomic context on realtime kernels (inside hard IRQ handlers and similar
261 The IRQ portions of the GPIO block are implemented using an irq_chip, using
265 It is legal for any IRQ consumer to request an IRQ from any irqchip even if it
266 is a combined GPIO+IRQ driver. The basic premise is that gpio_chip and
270 gpiod_to_irq() is just a convenience function to figure out the IRQ for a
272 the IRQ is used.
315 an SoC. This means that there is a fast IRQ flow handler for the GPIOs that
316 gets called in a chain from the parent IRQ handler, most typically the
331 Realtime considerations: Note that chained IRQ handlers will not be forced
333 runtime) can't be used in a chained IRQ handler.
336 see below) a chained IRQ handler can be converted to generic irq handler and
337 this way it will become a threaded IRQ handler on -RT and a hard IRQ handler
340 The generic_handle_irq() is expected to be called with IRQ disabled,
341 so the IRQ core will complain if it is called from an IRQ handler which is
353 but chained IRQ handlers are not used. Instead GPIO IRQs dispatching is
354 performed by generic IRQ handler which is configured using request_irq().
359 for each detected GPIO IRQ
363 and as result the IRQ core will complain that generic_handle_irq() is called
364 with IRQ enabled and the same work-around as for "CHAINED GPIO irqchips" can
371 Of course such drivers that need slow bus traffic to read out IRQ status and
373 handled in a quick IRQ handler with IRQs disabled. Instead they need to spawn
374 a thread and then mask the parent IRQ line until the interrupt is handled
402 :header: GPIO line offset, Hardware IRQ
486 /* This will let us handle the parent IRQ in the driver */
530 the IRQ, instead a parent irqdomain, an fwnode for the hardware and
536 If there is a need to exclude certain GPIO lines from the IRQ domain handled by
556 Locking IRQ usage
567 Input GPIOs can be used as IRQ signals. When this happens, a driver is requested
568 to mark the GPIO as being used as an IRQ::
572 This will prevent the use of non-irq related GPIO APIs until the GPIO IRQ lock
593 When a GPIO is used as an IRQ signal, then gpiolib also needs to know if
594 the IRQ is enabled or disabled. In order to inform gpiolib about this,
599 This allows drivers to drive the GPIO as an output while the IRQ is
600 disabled. When the IRQ is enabled again, a driver should call::
612 Real-Time compliance for GPIO IRQ chips
629 from the chained IRQ handler
632 - Chained GPIO irqchips: get rid of the chained IRQ handler and use generic irq