From: Johan Jonker <jbx6244@gmail.com>
To: heiko@sntech.de
Cc: robh+dt@kernel.org, kishon@ti.com, vkoul@kernel.org,
t.schramm@manjaro.org, linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v7 3/5] ARM: dts: rockchip: rename nodename for phy-rockchip-inno-usb2
Date: Tue, 1 Jun 2021 18:47:58 +0200 [thread overview]
Message-ID: <20210601164800.7670-4-jbx6244@gmail.com> (raw)
In-Reply-To: <20210601164800.7670-1-jbx6244@gmail.com>
The pattern: "^(|usb-|usb2-|usb3-|pci-|pcie-|sata-)phy(@[0-9a-f,]+)*$"
in phy-provider.yaml has required "#phy-cells" for phy nodes.
The "phy-cells" in rockchip-inno-usb2 nodes are located in subnodes.
Rename the nodename to pattern "usb2phy@[0-9a-f]+$" to prevent
notifications.
make ARCH=arm dtbs_check
DT_SCHEMA_FILES=~/.local/lib/python3.5/site-packages/dtschema/schemas/
phy/phy-provider.yaml
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
arch/arm/boot/dts/rk322x.dtsi | 4 ++--
arch/arm/boot/dts/rv1108.dtsi | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/rk322x.dtsi b/arch/arm/boot/dts/rk322x.dtsi
index 5774bc309..cffd7acfb 100644
--- a/arch/arm/boot/dts/rk322x.dtsi
+++ b/arch/arm/boot/dts/rk322x.dtsi
@@ -190,7 +190,7 @@
status = "disabled";
};
- u2phy0: usb2-phy@760 {
+ u2phy0: usb2phy@760 {
compatible = "rockchip,rk3228-usb2phy";
reg = <0x0760 0x0c>;
clocks = <&cru SCLK_OTGPHY0>;
@@ -217,7 +217,7 @@
};
};
- u2phy1: usb2-phy@800 {
+ u2phy1: usb2phy@800 {
compatible = "rockchip,rk3228-usb2phy";
reg = <0x0800 0x0c>;
clocks = <&cru SCLK_OTGPHY1>;
diff --git a/arch/arm/boot/dts/rv1108.dtsi b/arch/arm/boot/dts/rv1108.dtsi
index 884872ca5..9bd0acf3b 100644
--- a/arch/arm/boot/dts/rv1108.dtsi
+++ b/arch/arm/boot/dts/rv1108.dtsi
@@ -265,7 +265,7 @@
#address-cells = <1>;
#size-cells = <1>;
- u2phy: usb2-phy@100 {
+ u2phy: usb2phy@100 {
compatible = "rockchip,rv1108-usb2phy";
reg = <0x100 0x0c>;
clocks = <&cru SCLK_USBPHY>;
--
2.11.0
next prev parent reply other threads:[~2021-06-01 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:47 [PATCH v7 0/5] convert grf.txt to YAML Johan Jonker
2021-06-01 16:47 ` [PATCH v7 1/5] dt-bindings: phy: rename phy nodename in phy-rockchip-inno-usb2.yaml Johan Jonker
2021-06-03 5:54 ` Vinod Koul
2021-06-03 8:58 ` Heiko Stübner
2021-06-07 13:16 ` Rob Herring
2021-06-07 13:38 ` Johan Jonker
2021-06-07 14:18 ` [PATCH] dt-bindings: soc: rockchip: drop unnecessary #phy-cells from grf.yaml Heiko Stuebner
2021-06-07 15:37 ` Johan Jonker
2021-06-10 7:30 ` Heiko Stübner
2021-06-01 16:47 ` [PATCH v7 2/5] dt-bindings: soc: rockchip: grf: add compatible for RK3308 USB grf Johan Jonker
2021-06-02 18:17 ` Rob Herring
2021-06-01 16:47 ` Johan Jonker [this message]
2021-06-01 16:47 ` [PATCH v7 4/5] arm64: dts: rockchip: rename nodename for phy-rockchip-inno-usb2 Johan Jonker
2021-06-01 16:48 ` [PATCH v7 5/5] arm64: dts: rockchip: add USB support to rk3308.dtsi Johan Jonker
2021-06-03 9:56 ` [PATCH v7 0/5] convert grf.txt to YAML Heiko Stuebner
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=20210601164800.7670-4-jbx6244@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=t.schramm@manjaro.org \
--cc=vkoul@kernel.org \
/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).