-
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 tag 'irqchip-core-4.1-2' of git://git.infradead.org/users/jcoop…
…er/linux into irq/core irqchip core changes for v4.1 (round 2) from Jason Cooper - gic - Tolerate uni-processor systems better in gic_get_cpumask() - mvebu - Handle per-cpu interrupts properly - Enable PMU interrupts - Enable wakeup source - vybrid - Add MSCM interrupt router - renesas - Add PM and wakeup support
- Loading branch information
Showing
12 changed files
with
396 additions
and
41 deletions.
There are no files selected for viewing
14 changes: 14 additions & 0 deletions
14
Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm-cpucfg.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,14 @@ | ||
Freescale Vybrid Miscellaneous System Control - CPU Configuration | ||
|
||
The MSCM IP contains multiple sub modules, this binding describes the first | ||
block of registers which contains CPU configuration information. | ||
|
||
Required properties: | ||
- compatible: "fsl,vf610-mscm-cpucfg", "syscon" | ||
- reg: the register range of the MSCM CPU configuration registers | ||
|
||
Example: | ||
mscm_cpucfg: cpucfg@40001000 { | ||
compatible = "fsl,vf610-mscm-cpucfg", "syscon"; | ||
reg = <0x40001000 0x800>; | ||
} |
33 changes: 33 additions & 0 deletions
33
Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm-ir.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,33 @@ | ||
Freescale Vybrid Miscellaneous System Control - Interrupt Router | ||
|
||
The MSCM IP contains multiple sub modules, this binding describes the second | ||
block of registers which control the interrupt router. The interrupt router | ||
allows to configure the recipient of each peripheral interrupt. Furthermore | ||
it controls the directed processor interrupts. The module is available in all | ||
Vybrid SoC's but is only really useful in dual core configurations (VF6xx | ||
which comes with a Cortex-A5/Cortex-M4 combination). | ||
|
||
Required properties: | ||
- compatible: "fsl,vf610-mscm-ir" | ||
- reg: the register range of the MSCM Interrupt Router | ||
- fsl,cpucfg: The handle to the MSCM CPU configuration node, required | ||
to get the current CPU ID | ||
- interrupt-controller: Identifies the node as an interrupt controller | ||
- #interrupt-cells: Two cells, interrupt number and cells. | ||
The hardware interrupt number according to interrupt | ||
assignment of the interrupt router is required. | ||
Flags get passed only when using GIC as parent. Flags | ||
encoding as documented by the GIC bindings. | ||
- interrupt-parent: Should be the phandle for the interrupt controller of | ||
the CPU the device tree is intended to be used on. This | ||
is either the node of the GIC or NVIC controller. | ||
|
||
Example: | ||
mscm_ir: interrupt-controller@40001800 { | ||
compatible = "fsl,vf610-mscm-ir"; | ||
reg = <0x40001800 0x400>; | ||
fsl,cpucfg = <&mscm_cpucfg>; | ||
interrupt-controller; | ||
#interrupt-cells = <2>; | ||
interrupt-parent = <&intc>; | ||
} |
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.