Lines Matching +full:reverse +full:- +full:data

9 that each one gets assigned non-overlapping allocations of Linux
24 For this reason, we need a mechanism to separate controller-local
28 IRQ numbers, but they don't provide any support for reverse mapping of
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
35 reverse mapping scheme.
38 irq_fwspec to hwirq numbers (Device Tree, non-DT firmware node, ACPI
40 other IRQ topology data sources. The implementation is performed
53 The host code and data structures use a fwnode_handle pointer to
79 - irq_resolve_mapping() returns a pointer to the irq_desc structure
82 - irq_find_mapping() returns a Linux IRQ number for a given domain and
84 - generic_handle_domain_irq() handles an interrupt described by a
88 compatible with a RCU read-side critical section.
102 There are several mechanisms available for reverse mapping from hwirq
104 Which reverse map type should be used depends on the use case.  Each
105 of the reverse map types are described below:
108 ------
114 The linear reverse map maintains a fixed size table indexed by the
121 allocated for in-use IRQs.  The disadvantage is that the table must be
127 ----
145 ------
163 ------
186 visa-versa.  The disadvantage is that it requires the interrupt
192 mapping Linux IRQs 0-15 so that existing ISA drivers get the correct IRQ
199 will be allocated on-the-fly for it, and if no range is specified it
213 --------------------
219   Device --> IOAPIC -> Interrupt remapping Controller -> Local APIC -> CPU
228 hardware architecture, an irq_domain data structure is built for each
280 Note the hierarchy irq_domain is in no way x86-specific, and is
308 .. kernel-doc:: include/linux/irqdomain.h
310 .. kernel-doc:: kernel/irq/irqdomain.c
319 .. kernel-doc:: kernel/irq/irqdomain.c