-
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 'dt2' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/…
…arm-soc Pull ARM SoC device-tree updates, take 2, from Olof Johansson: "This branch contains device-tree updates for the SPEAr platform. They had dependencies on earlier branches from this merge window, which is why they were broken out in a separate branch." * tag 'dt2' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: ARM: SPEAr3xx: Shirq: Move shirq controller out of plat/ ARM: SPEAr320: DT: Add SPEAr 320 HMI board support ARM: SPEAr3xx: DT: add shirq node for interrupt multiplexor ARM: SPEAr3xx: shirq: simplify and move the shared irq multiplexor to DT ARM: SPEAr1310: Fix AUXDATA for compact flash controller ARM: SPEAr13xx: Remove fields not required for ssp controller ARM: SPEAr1310: Move 1310 specific misc register into machine specific files ARM: SPEAr: DT: Update device nodes ARM: SPEAr: DT: add uart state to fix warning ARM: SPEAr: DT: Modify DT bindings for STMMAC ARM: SPEAr: DT: Fix existing DT support ARM: SPEAr: DT: Update partition info for MTD devices ARM: SPEAr: DT: Update pinctrl list ARM: SPEAr13xx: DT: Add spics gpio controller nodes
- Loading branch information
Showing
31 changed files
with
1,428 additions
and
777 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
* SPEAr Shared IRQ layer (shirq) | ||
|
||
SPEAr3xx architecture includes shared/multiplexed irqs for certain set | ||
of devices. The multiplexor provides a single interrupt to parent | ||
interrupt controller (VIC) on behalf of a group of devices. | ||
|
||
There can be multiple groups available on SPEAr3xx variants but not | ||
exceeding 4. The number of devices in a group can differ, further they | ||
may share same set of status/mask registers spanning across different | ||
bit masks. Also in some cases the group may not have enable or other | ||
registers. This makes software little complex. | ||
|
||
A single node in the device tree is used to describe the shared | ||
interrupt multiplexor (one node for all groups). A group in the | ||
interrupt controller shares config/control registers with other groups. | ||
For example, a 32-bit interrupt enable/disable config register can | ||
accommodate upto 4 interrupt groups. | ||
|
||
Required properties: | ||
- compatible: should be, either of | ||
- "st,spear300-shirq" | ||
- "st,spear310-shirq" | ||
- "st,spear320-shirq" | ||
- interrupt-controller: Identifies the node as an interrupt controller. | ||
- #interrupt-cells: should be <1> which basically contains the offset | ||
(starting from 0) of interrupts for all the groups. | ||
- reg: Base address and size of shirq registers. | ||
- interrupts: The list of interrupts generated by the groups which are | ||
then connected to a parent interrupt controller. Each group is | ||
associated with one of the interrupts, hence number of interrupts (to | ||
parent) is equal to number of groups. The format of the interrupt | ||
specifier depends in the interrupt parent controller. | ||
|
||
Optional properties: | ||
- interrupt-parent: pHandle of the parent interrupt controller, if not | ||
inherited from the parent node. | ||
|
||
Example: | ||
|
||
The following is an example from the SPEAr320 SoC dtsi file. | ||
|
||
shirq: interrupt-controller@0xb3000000 { | ||
compatible = "st,spear320-shirq"; | ||
reg = <0xb3000000 0x1000>; | ||
interrupts = <28 29 30 1>; | ||
#interrupt-cells = <1>; | ||
interrupt-controller; | ||
}; |
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.