Lines Matching full:number

2 The irq_domain interrupt number mapping library
5 The current design of the Linux kernel uses a single large number
6 space where each separate IRQ source is assigned a different number.
12 The number of interrupt controllers registered as unique irqchips
18 Here the interrupt number loose all kind of correspondence to
22 interrupt line to the CPU) nowadays this number is just a number.
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
53 hwirq number as arguments.  If a mapping for the hwirq doesn't already
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
69   domain and a hwirq number
78 If the driver has the Linux IRQ number or the irq_data pointer, and
79 needs to know the associated hwirq number (such as in the irq_chip
99 hwirq number.  When a hwirq is mapped, an irq_desc is allocated for
100 the hwirq, and the IRQ number is stored in the table.
102 The Linear map is a good choice when the maximum number of hwirqs is
103 fixed and a relatively small number (~ < 256).  The advantages of this
106 as large as the largest possible hwirq number.
127 The tree map is a good choice if the hwirq number can be very large
129 hwirq number.  The disadvantage is that hwirq to IRQ number lookup is
146 The No Map mapping is to be used when the hwirq number 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.
181 been allocated for the controller and that the IRQ number can be
182 calculated by adding a fixed offset to the hwirq number, and
262    is used to store irq_domain pointer and hardware irq number.