forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/lin…
…ux/kernel/git/tip/tip Pull irq core updates from Thomas Gleixner: "A rather large update for the interrupt core code and the irq chip drivers: - Add a new bitmap matrix allocator and supporting changes, which is used to replace the x86 vector allocator which comes with separate pull request. This allows to replace the convoluted nested loop allocation function in x86 with a facility which supports the recently added property of managed interrupts proper and allows to switch to a best effort vector reservation scheme, which addresses problems with vector exhaustion. - A large update to the ARM GIC-V3-ITS driver adding support for range selectors. - New interrupt controllers: - Meson and Meson8 GPIO - BCM7271 L2 - Socionext EXIU If you expected that this will stop at some point, I have to disappoint you. There are new ones posted already. Sigh! - STM32 interrupt controller support for new platforms. - A pile of fixes, cleanups and updates to the MIPS GIC driver - The usual small fixes, cleanups and updates all over the place. Most visible one is to move the irq chip drivers Kconfig switches into a separate Kconfig menu" * 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (70 commits) genirq: Fix type of shifting literal 1 in __setup_irq() irqdomain: Drop pointless NULL check in virq_debug_show_one genirq/proc: Return proper error code when irq_set_affinity() fails irq/work: Use llist_for_each_entry_safe irqchip: mips-gic: Print warning if inherited GIC base is used irqchip/mips-gic: Add pr_fmt and reword pr_* messages irqchip/stm32: Move the wakeup on interrupt mask irqchip/stm32: Fix initial values irqchip/stm32: Add stm32h7 support dt-bindings/interrupt-controllers: Add compatible string for stm32h7 irqchip/stm32: Add multi-bank management irqchip/stm32: Select GENERIC_IRQ_CHIP irqchip/exiu: Add support for Socionext Synquacer EXIU controller dt-bindings: Add description of Socionext EXIU interrupt controller irqchip/gic-v3-its: Fix VPE activate callback return value irqchip: mips-gic: Make IPI bitmaps static irqchip: mips-gic: Share register writes in gic_set_type() irqchip: mips-gic: Remove gic_vpes variable irqchip: mips-gic: Use num_possible_cpus() to reserve IPIs irqchip: mips-gic: Configure EIC when CPUs come online ...
- Loading branch information
Showing
57 changed files
with
2,490 additions
and
408 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
36 changes: 36 additions & 0 deletions
36
Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
Amlogic meson GPIO interrupt controller | ||
|
||
Meson SoCs contains an interrupt controller which is able to watch the SoC | ||
pads and generate an interrupt on edge or level. The controller is essentially | ||
a 256 pads to 8 GIC interrupt multiplexer, with a filter block to select edge | ||
or level and polarity. It does not expose all 256 mux inputs because the | ||
documentation shows that the upper part is not mapped to any pad. The actual | ||
number of interrupt exposed depends on the SoC. | ||
|
||
Required properties: | ||
|
||
- compatible : must have "amlogic,meson8-gpio-intc” and either | ||
“amlogic,meson8-gpio-intc” for meson8 SoCs (S802) or | ||
“amlogic,meson8b-gpio-intc” for meson8b SoCs (S805) or | ||
“amlogic,meson-gxbb-gpio-intc” for GXBB SoCs (S905) or | ||
“amlogic,meson-gxl-gpio-intc” for GXL SoCs (S905X, S912) | ||
- interrupt-parent : a phandle to the GIC the interrupts are routed to. | ||
Usually this is provided at the root level of the device tree as it is | ||
common to most of the SoC. | ||
- reg : Specifies base physical address and size of the registers. | ||
- interrupt-controller : Identifies the node as an interrupt controller. | ||
- #interrupt-cells : Specifies the number of cells needed to encode an | ||
interrupt source. The value must be 2. | ||
- meson,channel-interrupts: Array with the 8 upstream hwirq numbers. These | ||
are the hwirqs used on the parent interrupt controller. | ||
|
||
Example: | ||
|
||
gpio_interrupt: interrupt-controller@9880 { | ||
compatible = "amlogic,meson-gxbb-gpio-intc", | ||
"amlogic,meson-gpio-intc"; | ||
reg = <0x0 0x9880 0x0 0x10>; | ||
interrupt-controller; | ||
#interrupt-cells = <2>; | ||
meson,channel-interrupts = <64 65 66 67 68 69 70 71>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
32 changes: 32 additions & 0 deletions
32
Documentation/devicetree/bindings/interrupt-controller/socionext,synquacer-exiu.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
Socionext SynQuacer External Interrupt Unit (EXIU) | ||
|
||
The Socionext Synquacer SoC has an external interrupt unit (EXIU) | ||
that forwards a block of 32 configurable input lines to 32 adjacent | ||
level-high type GICv3 SPIs. | ||
|
||
Required properties: | ||
|
||
- compatible : Should be "socionext,synquacer-exiu". | ||
- reg : Specifies base physical address and size of the | ||
control registers. | ||
- interrupt-controller : Identifies the node as an interrupt controller. | ||
- #interrupt-cells : Specifies the number of cells needed to encode an | ||
interrupt source. The value must be 3. | ||
- interrupt-parent : phandle of the GIC these interrupts are routed to. | ||
- socionext,spi-base : The SPI number of the first SPI of the 32 adjacent | ||
ones the EXIU forwards its interrups to. | ||
|
||
Notes: | ||
|
||
- Only SPIs can use the EXIU as an interrupt parent. | ||
|
||
Example: | ||
|
||
exiu: interrupt-controller@510c0000 { | ||
compatible = "socionext,synquacer-exiu"; | ||
reg = <0x0 0x510c0000 0x0 0x20>; | ||
interrupt-controller; | ||
interrupt-parent = <&gic>; | ||
#interrupt-cells = <3>; | ||
socionext,spi-base = <112>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.