Lines Matching full:hwirq

29 the controller-local IRQ (hwirq) number into the Linux IRQ number
32 The irq_domain library adds a mapping between hwirq and IRQ numbers on
38 irq_fwspec to hwirq numbers (Device Tree, non-DT firmware node, ACPI
68 between hwirq and IRQ numbers.  Mappings are added to the irq_domain
70 hwirq number as arguments. If a mapping for the hwirq doesn't already
72 it with the hwirq, and calls the :c:member:`irq_domain_ops.map()`
80   for a given domain and hwirq number, and NULL if there was no
83   hwirq number, and 0 if there was no mapping
85   domain and a hwirq number
95 needs to know the associated hwirq number (such as in the irq_chip
97 :c:member:`irq_data.hwirq`.
102 There are several mechanisms available for reverse mapping from hwirq
115 hwirq number.  When a hwirq is mapped, an irq_desc is allocated for
116 the hwirq, and the IRQ number is stored in the table.
122 as large as the largest possible hwirq number.
133 The irq_domain maintains a radix tree map from hwirq numbers to Linux
134 IRQs.  When an hwirq is mapped, an irq_desc is allocated and the
135 hwirq is used as the lookup key for the radix tree.
137 The tree map is a good choice if the hwirq number can be very large
139 hwirq number.  The disadvantage is that hwirq to IRQ number lookup is
151 The No Map mapping is to be used when the hwirq number is
185 calculated by adding a fixed offset to the hwirq number, and
188 allocated for every hwirq, even if it is unused.