Skip to main content

Browse the archive

https://github.com/torvalds/linux
05 April 2024, 19:05:47 UTC
Revision 228f1ce9b8e9e63c3ffc1b03b64d77277cacb89f authored by Barry Song on 04 February 2013, 09:53:34 UTC, committed by Linus Walleij on 05 February 2013, 14:27:39 UTC 
pinctrl: sirf: replace of_gpio_simple_xlate by sirf specific of_xlate
 
the default of_gpio_simple_xlate() will make us fail while getting gpios
bigger than 32 by of_get_named_gpio() or related APIs.
this patch adds a specific of_xlate callback for sirf gpio_chip and fix
the problem.

Signed-off-by: Barry Song <Baohua.Song@csr.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
1 parent a1ed267
Raw File
Tip revision: 228f1ce9b8e9e63c3ffc1b03b64d77277cacb89f authored by Barry Song on 04 February 2013, 09:53:34 UTC
pinctrl: sirf: replace of_gpio_simple_xlate by sirf specific of_xlate
Tip revision: 228f1ce
IRQ.txt 
What is an IRQ?

An IRQ is an interrupt request from a device.
Currently they can come in over a pin, or over a packet.
Several devices may be connected to the same pin thus
sharing an IRQ.

An IRQ number is a kernel identifier used to talk about a hardware
interrupt source.  Typically this is an index into the global irq_desc
array, but except for what linux/interrupt.h implements the details
are architecture specific.

An IRQ number is an enumeration of the possible interrupt sources on a
machine.  Typically what is enumerated is the number of input pins on
all of the interrupt controller in the system.  In the case of ISA
what is enumerated are the 16 input pins on the two i8259 interrupt
controllers.

Architectures can assign additional meaning to the IRQ numbers, and
are encouraged to in the case  where there is any manual configuration
of the hardware involved.  The ISA IRQs are a classic example of
assigning this kind of additional meaning.
back to top