Lines Matching refs:IRQ

6 space where each separate IRQ source is assigned a different number.
10 IRQ numbers.
15 mechanisms as the IRQ core system by modelling their interrupt
19 hardware interrupt numbers: whereas in the past, IRQ numbers could
20 be chosen so they matched the hardware IRQ line into the root
25 interrupt numbers, called hardware irq's, from Linux IRQ numbers.
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
32 The irq_domain library adds mapping between hwirq and IRQ numbers on
39 be easily extended to support other IRQ topology data sources.
51 between hwirq and IRQ numbers. Mappings are added to the irq_domain
64 - irq_find_mapping() returns a Linux IRQ number for a given domain and
78 If the driver has the Linux IRQ number or the irq_data pointer, and
100 the hwirq, and the IRQ number is stored in the table.
104 map are fixed time lookup for IRQ numbers, and irq_descs are only
129 hwirq number. The disadvantage is that hwirq to IRQ number lookup is
148 Linux IRQ number into the hardware itself so that no mapping is
150 IRQ number and call the .map() callback so that driver can program the
151 Linux IRQ number into the hardware.
171 for IRQ numbers that are passed to struct device registrations. In that
172 case the Linux IRQ numbers cannot be dynamically assigned and the legacy
180 The legacy map assumes a contiguous range of IRQ numbers has already
181 been allocated for the controller and that the IRQ number can be
184 controller to manage IRQ allocations and it requires an irq_desc to be
187 The legacy map should only be used if fixed IRQ mappings must be
189 mapping Linux IRQs 0-15 so that existing ISA drivers get the correct IRQ
193 irq_domain_create_simple() which will use a legacy domain only if an IRQ range
195 The semantics of this call are such that if an IRQ range is specified then
201 is supporting both dynamic and static IRQ assignments.
207 for the static IRQ assignment case.
215 Hierarchy IRQ domain
247 1) irq_domain_alloc_irqs(): allocate IRQ descriptors and interrupt
249 2) irq_domain_free_irqs(): free IRQ descriptors and interrupt controller
269 IRQ. Now we could go one step further to support stacked(hierarchy)
296 Most of the internals of the IRQ subsystem are exposed in debugfs by