From: Orson Zhai <orson.zhai@unisoc.com>
To: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<steven.tang@unisoc.com>, Orson Zhai <orson.zhai@unisoc.com>
Subject: [PATCH 1/2] dt-bindings: Add syscon-names support
Date: Thu, 14 Nov 2019 19:45:24 +0800 [thread overview]
Message-ID: <20191114114525.12675-2-orson.zhai@unisoc.com> (raw)
In-Reply-To: <20191114114525.12675-1-orson.zhai@unisoc.com>
Make life easier when syscon consumer want to access multiple syscon
nodes.
Add syscon-names and relative properties to help manage complicated
cases when accessing more one syscon node.
Signed-off-by: Orson Zhai <orson.zhai@unisoc.com>
---
.../devicetree/bindings/mfd/syscon.txt | 36 +++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/syscon.txt b/Documentation/devicetree/bindings/mfd/syscon.txt
index 25d9e9c2fd53..ca7bc7608c15 100644
--- a/Documentation/devicetree/bindings/mfd/syscon.txt
+++ b/Documentation/devicetree/bindings/mfd/syscon.txt
@@ -17,6 +17,8 @@ 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.
+- #syscon-cells: represents the number of args. Used when syscon-names
+ is going to be used. The value is vendor specific.
Examples:
gpr: iomuxc-gpr@20e0000 {
@@ -30,3 +32,37 @@ hwlock1: hwspinlock@40500000 {
reg = <0x40500000 0x1000>;
#hwlock-cells = <1>;
};
+
+
+==Syscon names==
+
+Refer to syscon node by names with phandle args in syscon consumer node.
+
+Required properties:
+- syscons: List of phandle and any number of args. Args is specific to
+ differnet vendor. For example: In Unisoc SoCs, the 1st arg
+ will be treated as register address offset and the 2nd is bit
+ mask as default.
+
+- syscon-names: List of syscon node name strings sorted in the same
+ order as the syscons property.
+
+Examples:
+
+apb_regs: syscon@20008000 {
+ compatible = "sprd,apb-glb", "syscon";
+ #syscon-cells = <2>;
+ reg = <0x20008000 0x100>;
+};
+
+aon_regs: syscon@40008000 {
+ compatible = "sprd,aon-glb", "syscon";
+ #syscon-cells = <1>;
+ reg = <0x40008000 0x100>;
+};
+
+display@40500000 {
+ ...
+ syscons = <&ap_apb_regs 0x4 0xf00>, <&aon_regs 0x8>;
+ syscon-names = "enable", "power";
+};
--
2.18.0
next prev parent reply other threads:[~2019-11-14 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 11:45 [PATCH 0/2] Add syscon name and #cells support Orson Zhai
2019-11-14 11:45 ` Orson Zhai [this message]
2019-11-15 9:33 ` [PATCH 1/2] dt-bindings: Add syscon-names support Arnd Bergmann
2019-11-18 8:39 ` Orson Zhai
2019-11-19 14:20 ` Arnd Bergmann
2019-11-19 14:46 ` Arnd Bergmann
2019-11-20 15:49 ` Orson Zhai
2019-11-14 11:45 ` [PATCH 2/2] mfd: syscon: Add syscon-names and phandle args support Orson Zhai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191114114525.12675-2-orson.zhai@unisoc.com \
--to=orson.zhai@unisoc.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=steven.tang@unisoc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®