dt-bindings: Add syscon YAML description
PATCH v2 1/1 dt-bindings: Add syscon YAML description
The syscon binding is a pretty loose one, with everyone having a bunch of vendor specific compatibles.
In order to start the effort to describe them using YAML, let's create a binding that tolerates additional, not listed, compatibles.
Signed-off-by Maxime Ripard <[email protected]>
---
Changes from v1:
- Move syscon binding from misc to mfd
- Add a select statement
--- .../devicetree/bindings/mfd/syscon.txt | 32 ------- .../devicetree/bindings/mfd/syscon.yaml | 84 +++++++++++++++++++ .../bindings/misc/allwinner,syscon.txt | 20 ----- 3 files changed, 84 insertions(+), 52 deletions(-) delete mode 100644 Documentation/devicetree/bindings/mfd/syscon.txt create mode 100644 Documentation/devicetree/bindings/mfd/syscon.yaml delete mode 100644 Documentation/devicetree/bindings/misc/allwinner,syscon.txt
Documentation/devicetree/bindings/mfd/syscon.txt deleted +0 -32
@@ -1,32 +0,0 @@ -* System Controller Registers R/W driver - -System controller node represents a register region containing a set -of miscellaneous registers. The registers are not cohesive enough to -represent as any specific type of device. The typical use-case is for -some other node's driver, or platform-specific code, to acquire a -reference to the syscon node (e.g. by phandle, node path, or search -using a specific compatible value), interrogate the node (or associated -OS driver) to determine the location of the registers, and access the -registers directly. - -Required properties: -- compatible: Should contain "syscon". -- reg: the register region can be accessed from syscon - -Optional property: -- reg-io-width: the size (in bytes) of the IO accesses that should be - performed on the device. -- hwlocks: reference to a phandle of a hardware spinlock provider node. - -Examples: -gpr: iomuxc-gpr@20e0000 { - compatible = "fsl,imx6q-iomuxc-gpr", "syscon"; - reg = <0x020e0000 0x38>; - hwlocks = <&hwlock1 1>; -}; - -hwlock1: hwspinlock@40500000 { - ... - reg = <0x40500000 0x1000>; - #hwlock-cells = <1>; -};
Documentation/devicetree/bindings/mfd/syscon.yaml new file +84 -0
84 lines not on this page · raw message
Documentation/devicetree/bindings/misc/allwinner,syscon.txt deleted +0 -20
@@ -1,20 +0,0 @@ -* Allwinner sun8i system controller - -This file describes the bindings for the system controller present in -Allwinner SoC H3, A83T and A64. -The principal function of this syscon is to control EMAC PHY choice and -config. - -Required properties for the system controller: -- reg: address and length of the register for the device. -- compatible: should be "syscon" and one of the following string: - "allwinner,sun8i-h3-system-controller" - "allwinner,sun8i-v3s-system-controller" - "allwinner,sun50i-a64-system-controller" - "allwinner,sun8i-a83t-system-controller" - -Example: -syscon: syscon@1c00000 { - compatible = "allwinner,sun8i-h3-system-controller", "syscon"; - reg = <0x01c00000 0x1000>; -};
Signature · 1 line
2.23.0
Quoted 13 lines · Maxime Ripard
The syscon binding is a pretty loose one, with everyone having a bunch of vendor specific compatibles.
In order to start the effort to describe them using YAML, let's create a binding that tolerates additional, not listed, compatibles.
Signed-off-by Maxime Ripard <[email protected]>---
Changes from v1:
- Move syscon binding from misc to mfd
- Add a select statement
Quoted 9 lines
--- .../devicetree/bindings/mfd/syscon.txt | 32 ------- .../devicetree/bindings/mfd/syscon.yaml | 84 +++++++++++++++++++ .../bindings/misc/allwinner,syscon.txt | 20 ----- 3 files changed, 84 insertions(+), 52 deletions(-) delete mode 100644 Documentation/devicetree/bindings/mfd/syscon.txt create mode 100644 Documentation/devicetree/bindings/mfd/syscon.yaml delete mode 100644 Documentation/devicetree/bindings/misc/allwinner,syscon.txt
Applied, thanks.
Rob