redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

dt-bindings: hwlock: Update OMAP binding for TI K3 SoCs 

The TI K3 AM65x and J721E family of SoCs have a HwSpinlock IP that
is similar to the existing HwSpinlock IP present in OMAP architecture
based SoCs with minor differences. Update the existing OMAP HwSpinlock
binding for this IP on TI K3 AM65x and J721E SoCs. The same compatible
from AM65x SoCs is reused for J721E SoCs.

Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
alistair/sunxi64-5.4-dsi
Suman Anna 2019-05-30 21:13:19 -05:00 committed by Bjorn Andersson
parent a188339ca5
commit 7f40c260df
1 changed files with 20 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
Documentation/devicetree/bindings/hwlock/omap-hwspinlock.txt
View File

@ -1,12 +1,16 @@
OMAP4+ HwSpinlock Driver TI HwSpinlock for OMAP and K3 based SoCs
======================== =========================================
Required properties: Required properties:
- compatible: Should be "ti,omap4-hwspinlock" for - compatible: Should be one of the following,
OMAP44xx, OMAP54xx, AM33xx, AM43xx, DRA7xx SoCs "ti,omap4-hwspinlock" for
OMAP44xx, OMAP54xx, AM33xx, AM43xx, DRA7xx SoCs
"ti,am654-hwspinlock" for
K3 AM65x and J721E SoCs
- reg: Contains the hwspinlock module register address space - reg: Contains the hwspinlock module register address space
(base address and length) (base address and length)
- ti,hwmods: Name of the hwmod associated with the hwspinlock device - ti,hwmods: Name of the hwmod associated with the hwspinlock device
(for OMAP architecture based SoCs only)
- #hwlock-cells: Should be 1. The OMAP hwspinlock users will use a - #hwlock-cells: Should be 1. The OMAP hwspinlock users will use a
0-indexed relative hwlock number as the argument 0-indexed relative hwlock number as the argument
specifier value for requesting a specific hwspinlock specifier value for requesting a specific hwspinlock
@ -17,10 +21,21 @@ Please look at the generic hwlock binding for usage information for consumers,
Example: Example:
/* OMAP4 */ 1. OMAP4 SoCs
hwspinlock: spinlock@4a0f6000 { hwspinlock: spinlock@4a0f6000 {
compatible = "ti,omap4-hwspinlock"; compatible = "ti,omap4-hwspinlock";
reg = <0x4a0f6000 0x1000>; reg = <0x4a0f6000 0x1000>;
ti,hwmods = "spinlock"; ti,hwmods = "spinlock";
#hwlock-cells = <1>; #hwlock-cells = <1>;
}; };
2. AM65x SoCs and J721E SoCs
&cbass_main {
cbass_main_navss: interconnect0 {
hwspinlock: spinlock@30e00000 {
compatible = "ti,am654-hwspinlock";
reg = <0x00 0x30e00000 0x00 0x1000>;
#hwlock-cells = <1>;
};
};
};