From: Peter Geis <pgwipeout@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
Yifeng Zhao <yifeng.zhao@rock-chips.com>,
Johan Jonker <jbx6244@gmail.com>
Cc: linux-rockchip@lists.infradead.org,
michael.riesch@wolfvision.net, Peter Geis <pgwipeout@gmail.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 1/8] dt-bindings: soc: grf: fix rk3568 usb definitions
Date: Mon, 28 Feb 2022 08:56:52 -0500 [thread overview]
Message-ID: <20220228135700.1089526-2-pgwipeout@gmail.com> (raw)
In-Reply-To: <20220228135700.1089526-1-pgwipeout@gmail.com>
The rockchip,rk3568-pipe-grf and rockchip,rk3568-pipe-phy-grf
compatibles were incorrectly assigned to the syscon, simple-mfd
enumeration, vice only the syscon enumeration.
This leads a dtbs_check failure.
Move these to the syscon enumeration.
Fixes: b3df807e1fb0 ("dt-bindings: soc: grf: add naneng combo phy register compatible")
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
index 072318fcd57b..5079e9d24af6 100644
--- a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
+++ b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
@@ -15,6 +15,8 @@ properties:
- items:
- enum:
- rockchip,rk3288-sgrf
+ - rockchip,rk3568-pipe-grf
+ - rockchip,rk3568-pipe-phy-grf
- rockchip,rk3568-usb2phy-grf
- rockchip,rv1108-usbgrf
- const: syscon
@@ -39,8 +41,6 @@ properties:
- rockchip,rk3399-grf
- rockchip,rk3399-pmugrf
- rockchip,rk3568-grf
- - rockchip,rk3568-pipe-grf
- - rockchip,rk3568-pipe-phy-grf
- rockchip,rk3568-pmugrf
- rockchip,rv1108-grf
- rockchip,rv1108-pmugrf
--
2.25.1
next prev parent reply other threads:[~2022-02-28 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:56 [PATCH v4 0/8] enable usb support on rk356x Peter Geis
2022-02-28 13:56 ` Peter Geis [this message]
2022-03-01 14:52 ` [PATCH v4 1/8] dt-bindings: soc: grf: fix rk3568 usb definitions Peter Geis
2022-03-02 8:16 ` Vinod Koul
2022-03-02 12:18 ` Peter Geis
2022-03-02 14:22 ` Vinod Koul
2022-02-28 13:56 ` [PATCH v4 2/8] dt-bindings: soc: grf: add rk3566-pipe-grf compatible Peter Geis
2022-03-07 23:10 ` Rob Herring
2022-02-28 13:56 ` [PATCH v4 3/8] dt-bindings: usb: add rk3568 compatible to rockchip, dwc3 Peter Geis
2022-03-07 23:10 ` Rob Herring
2022-02-28 13:56 ` [PATCH v4 6/8] arm64: dts: rockchip: add rk356x dwc3 usb3 nodes Peter Geis
2022-03-03 16:05 ` Aw: " Frank Wunderlich
2022-02-28 13:56 ` [PATCH v4 7/8] arm64: dts: rockchip: enable dwc3 on quartz64-a Peter Geis
2022-02-28 13:56 ` [PATCH v4 8/8] arm64: dts: rockchip: add usb3 support to rk3568-evb1-v10 Peter Geis
2022-03-01 14:30 ` [PATCH v4 0/8] enable usb support on rk356x Michael Riesch
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=20220228135700.1089526-2-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=yifeng.zhao@rock-chips.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).