From: Heiko Stuebner <heiko@sntech.de>
To: heiko@sntech.de
Cc: michael.riesch@wolfvision.net,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@kernel.org>
Subject: [PATCH] arm64: dts: rockchip: fix nodename warning on wolfvision-pf5-display
Date: Tue, 23 Apr 2024 10:29:41 +0200 [thread overview]
Message-ID: <20240423082941.2626102-1-heiko@sntech.de> (raw)
The dtbs check throws a warning about node naming with the recently
added pf5-display-overlay:
rockchip/rk3568-wolfvision-pf5-display.dtsi:113.6-121.3: Warning (graph_port): /fragment@4/__overlay__: graph port node name should be 'port'
This comes from the overlay just referencing the vp2-port-node via
its phandle and then adding an endpoint beneath it.
While this is possible something to handle inside the dtbs check,
carrying around the warning is not pretty, so change the description
to go around it.
Starting from the vop_out phandle and then referencing the port
via its generic port@2 nodename will satisfy the port<->endpoint
naming dependency while keeping the same structure once the overlay
is applied.
Reported-by: Arnd Bergmann <arnd@kernel.org>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
---
.../rockchip/rk3568-wolfvision-pf5-display.dtsi | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3568-wolfvision-pf5-display.dtsi b/arch/arm64/boot/dts/rockchip/rk3568-wolfvision-pf5-display.dtsi
index b22bb543ecbb..18c807c39e56 100644
--- a/arch/arm64/boot/dts/rockchip/rk3568-wolfvision-pf5-display.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3568-wolfvision-pf5-display.dtsi
@@ -110,12 +110,14 @@ &pwm10 {
status = "okay";
};
-&vp2 {
- #address-cells = <1>;
- #size-cells = <0>;
+&vop_out {
+ port@2 {
+ #address-cells = <1>;
+ #size-cells = <0>;
- vp2_out_rgb: endpoint@ROCKCHIP_VOP2_EP_RGB0 {
- reg = <ROCKCHIP_VOP2_EP_RGB0>;
- remote-endpoint = <&panel_in_vp2>;
+ vp2_out_rgb: endpoint@ROCKCHIP_VOP2_EP_RGB0 {
+ reg = <ROCKCHIP_VOP2_EP_RGB0>;
+ remote-endpoint = <&panel_in_vp2>;
+ };
};
};
--
2.39.2
next reply other threads:[~2024-04-23 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 8:29 Heiko Stuebner [this message]
2024-04-23 9:39 ` [PATCH] arm64: dts: rockchip: fix nodename warning on wolfvision-pf5-display Michael Riesch
2024-04-23 11:03 ` Heiko Stübner
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=20240423082941.2626102-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=arnd@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
/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