[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191103013645.9856-10-afaerber@suse.de>
Date: Sun, 3 Nov 2019 02:36:43 +0100
From: Andreas Färber <afaerber@...e.de>
To: linux-realtek-soc@...ts.infradead.org
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Andreas Färber <afaerber@...e.de>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org
Subject: [RFC 09/11] dt-bindings: soc: realtek: rtd1195-chip: Extend reg node again
Allow to optionally specify a third register to identify the chip.
Whether needed and which register to specify depends on the family;
RTD1295 family will want an efuse register.
Signed-off-by: Andreas Färber <afaerber@...e.de>
---
I don't like specifying an efuse register here, which seems its own IP block.
.../devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml b/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml
index e431cf559b66..249737e116d7 100644
--- a/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml
+++ b/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml
@@ -19,7 +19,7 @@ properties:
reg:
minItems: 1
- maxItems: 2
+ maxItems: 3
required:
- compatible
@@ -37,4 +37,11 @@ examples:
reg = <0x9801a200 0x8>,
<0x98007028 0x4>;
};
+ - |
+ chip-info@...1a200 {
+ compatible = "realtek,rtd1195-chip";
+ reg = <0x9801a200 0x8>,
+ <0x98007028 0x4>,
+ <0x980171d8 0x4>;
+ };
...
--
2.16.4
Powered by blists - more mailing lists