Lines Matching refs:line
67 hardware interrupts are combined into one line that is then routed to
93 * '-' means interrupt line and is numbered from 0 (right most).
95 to nested controllers and one device 'A' on line 4.
96 * One of the LEVEL 2 controllers has interrupt line 5 connected to
97 a LEVEL 3 nested controller and one device 'C' on line 3.
99 device 'B' on line 2.
100 * The LEVEL 3 controller has one device 'D' on line 2.
116 controller has device D on line 2, connected to the LEVEL 2 controller's line
117 5, that is connected to the LEVEL 1 controller's line 9 (2 -> 5 -> 9).
230 a second ISR/argument pair on the same interrupt line is made (using
231 :c:macro:`IRQ_CONNECT` or :c:func:`irq_connect_dynamic`), the interrupt line will
234 The entities that make use of an interrupt line in the shared interrupt context
244 After an ISR is disconnected, whenever the interrupt line for which it was
361 Sharing an interrupt line
498 /** IRQ line number */
539 for IRQ line n, and the function pointers are:
573 argument and execute it. The active IRQ line is looked up in an interrupt
589 lines. Whenever an interrupt line becomes shared, :c:func:`z_shared_isr` will
613 /** IRQ line number */
682 systems the indexes in the vector table do not correspond to the IRQ line. The
692 indexed by IRQ line is not used. Instead, the :c:macro:`IRQ_CONNECT` call
701 runtime what vector is associated with an IRQ line. :ref:`gen_idt.py` additionally
702 creates an _irq_to_interrupt_vector array which maps an IRQ line to its