linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: jbx6244@gmail.com
Cc: robh+dt@kernel.org, vkoul@kernel.org, kishon@ti.com,
	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, Heiko Stuebner <heiko@sntech.de>
Subject: [PATCH] dt-bindings: soc: rockchip: drop unnecessary #phy-cells from grf.yaml
Date: Mon,  7 Jun 2021 16:18:45 +0200	[thread overview]
Message-ID: <20210607141845.3331910-1-heiko@sntech.de> (raw)
In-Reply-To: <e7e09072-9cac-413e-dca2-e2a668c1807e@gmail.com>

The recent yaml conversion of the grf and inno-usb2-phy bindings
left the #phy-cells in place in the main usb2phy node inside the
example in grf.yaml, causing new warnings.

Drop it to make the bindingcheck happy.

Fixes: e71ccdff376b ("dt-bindings: phy: rename phy nodename in phy-rockchip-inno-usb2.yaml")
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
---
Like this I guess?

 Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
index 8c1c46fef157..62fa72cfea34 100644
--- a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
+++ b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
@@ -242,7 +242,6 @@ examples:
         clock-names = "phyclk";
         #clock-cells = <0>;
         clock-output-names = "clk_usbphy0_480m";
-        #phy-cells = <0>;
 
         u2phy0_host: host-port {
           #phy-cells = <0>;
-- 
2.29.2


  reply	other threads:[~2021-06-07 14:18 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           ` Heiko Stuebner [this message]
2021-06-07 15:37             ` [PATCH] dt-bindings: soc: rockchip: drop unnecessary #phy-cells from grf.yaml 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 ` [PATCH v7 3/5] ARM: dts: rockchip: rename nodename for phy-rockchip-inno-usb2 Johan Jonker
2021-06-01 16:47 ` [PATCH v7 4/5] arm64: " 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=20210607141845.3331910-1-heiko@sntech.de \
    --to=heiko@sntech.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jbx6244@gmail.com \
    --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).