Lines Matching +full:no +full:- +full:map

9 that each one gets assigned non-overlapping allocations of Linux
24 For this reason we need a mechanism to separate controller-local
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
55 the hwirq, and call the .map() callback so the driver can perform any
61 - irq_resolve_mapping() returns a pointer to the irq_desc structure
62   for a given domain and hwirq number, and NULL if there was no
64 - irq_find_mapping() returns a Linux IRQ number for a given domain and
65   hwirq number, and 0 if there was no mapping
66 - irq_linear_revmap() is now identical to irq_find_mapping(), and is
68 - generic_handle_domain_irq() handles an interrupt described by a
70 - handle_domain_irq() does the same thing for root interrupt
75 compatible with a RCU read-side critical section.
83 callbacks) then it can be directly obtained from irq_data->hwirq.
90 Which reverse map type should be used depends on the use case.  Each
91 of the reverse map types are described below:
94 ------
101 The linear reverse map maintains a fixed size table indexed by the
105 The Linear map is a good choice when the maximum number of hwirqs is
107 map are fixed time lookup for IRQ numbers, and irq_descs are only
108 allocated for in-use IRQs.  The disadvantage is that the table must be
112 equivalent, except for the first argument is different - the former
116 The majority of drivers should use the linear map.
119 ----
126 The irq_domain maintains a radix tree map from hwirq numbers to Linux
130 The tree map is a good choice if the hwirq number can be very large
136 equivalent, except for the first argument is different - the former
142 No Map
143 ------
149 The No Map mapping is to be used when the hwirq number is
151 Linux IRQ number into the hardware itself so that no mapping is
153 IRQ number and call the .map() callback so that driver can program the
161 ------
179 exist to ease the support of ancient platforms. No new users should be
183 The legacy map assumes a contiguous range of IRQ numbers has already
186 visa-versa.  The disadvantage is that it requires the interrupt
190 The legacy map should only be used if fixed IRQ mappings must be
191 supported.  For example, ISA controllers would use the legacy map for
192 mapping Linux IRQs 0-15 so that existing ISA drivers get the correct IRQ
199 descriptors will be allocated on-the-fly for it, and if no range is
201 irq_domain_create_linear() which means *no* irq descriptors will be allocated.
207 used and no descriptor gets allocated it is very important to make sure
214 equivalent, except for the first argument is different - the former
219 --------------------
225   Device --> IOAPIC -> Interrupt remapping Controller -> Local APIC -> CPU
290 4) No need to implement irq_domain_ops.map and irq_domain_ops.unmap,
293 Hierarchy irq_domain is in no way x86 specific, and is heavily used to