Lines Matching full:an

33 top of the irq_alloc_desc*() API.  An irq_domain to manage mapping is
37 irq_domain also implements translation from an abstract irq_fwspec
44 An interrupt controller driver creates and registers an irq_domain by
48 provide the allocator function with an irq_domain_ops structure.
58 When an interrupt is received, irq_find_mapping() function should
86 hwirq number.  When a hwirq is mapped, an irq_desc is allocated for
97 accepts an Open Firmware specific 'struct device_node', while the latter
111 IRQs.  When an hwirq is mapped, an irq_desc is allocated and the
121 accepts an Open Firmware specific 'struct device_node', while the latter
163 controller to manage IRQ allocations and it requires an irq_desc to be
172 will use a legacy domain only if an IRQ range is supplied by the
174 of this call are such that if an IRQ range is specified then
179 A typical use case for simple domains is where an irqchip provider
192 involved in delivering an interrupt from the device to the target CPU.
204 hardware architecture, an irq_domain data structure is built for each
239 With support of hierarchy irq_domain and hierarchy irq_data ready, an
240 irq_domain structure is built for each interrupt controller, and an
241 irq_data structure is allocated for each irq_domain associated with an
243 irq_chip. That is, an irq_chip is associated with each irq_data along
252 For an interrupt controller driver to support hierarchy irq_domain, it
258 3) Optionally implement an irq_chip to manage the interrupt controller