From: Simon Horman <horms+renesas@verge.net.au>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Gross <agross@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Kaneko <ykaneko0929@gmail.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH v4 3/3] arm64: dts: qcom: msm8996: Update simple-pm-bus node name to 'bus'
Date: Mon, 30 Sep 2019 13:52:05 +0200 [thread overview]
Message-ID: <20190930115205.25204-4-horms+renesas@verge.net.au> (raw)
In-Reply-To: <20190930115205.25204-1-horms+renesas@verge.net.au>
Update simple-pm-bus node name from 'agnoc' to 'bus' reflecting the
proposed binding description in json-schema which in turn reflects the
Devicetree specification [1] v0.3-rc2.
"The name of a node should be somewhat generic, reflecting the function
of the device and not its precise programming model. If appropriate,
the name should be one of the following choices:
...
* bus
..."
Also drop the unit address as there is neither a reg property nor
non-empty ranges.
[1] https://www.devicetree.org/specifications/
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
*** Compile tested only ***
v4
* Update changelog
* Update reference in apq8096-db820c.dtsi
v3
* v2 was miss-posted as v3
v2
* New patch
---
arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 2 +-
arch/arm64/boot/dts/qcom/msm8996.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi b/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi
index 04ad2fb22b9a..5a2297777592 100644
--- a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi
+++ b/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi
@@ -439,7 +439,7 @@
enable-active-high;
};
- agnoc@0 {
+ bus {
pcie@600000 {
status = "okay";
perst-gpio = <&msmgpio 35 GPIO_ACTIVE_LOW>;
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index 96c0a481f454..99f376ebd27e 100644
--- a/arch/arm64/boot/dts/qcom/msm8996.dtsi
+++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi
@@ -1373,7 +1373,7 @@
clock-names = "iface", "bus";
};
- agnoc@0 {
+ bus {
power-domains = <&gcc AGGRE0_NOC_GDSC>;
compatible = "simple-pm-bus";
#address-cells = <1>;
--
2.11.0
prev parent reply other threads:[~2019-09-30 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 11:52 [PATCH v4 0/3] dt-bindings: bus: simple-pm-bus, renesas-bsc: convert bindings to json-schema Simon Horman
2019-09-30 11:52 ` [PATCH v4 1/3] dt-bindings: bus: simple-pm-bus: " Simon Horman
2019-10-01 13:41 ` Rob Herring
2019-09-30 11:52 ` [PATCH v4 2/3] dt-bindings: bus: renesas-bsc: " Simon Horman
2019-10-01 13:42 ` Rob Herring
2019-09-30 11:52 ` Simon Horman [this message]
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=20190930115205.25204-4-horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ykaneko0929@gmail.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;
as well as URLs for NNTP newsgroup(s).