From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Cc: lst@pengutronix.de
Subject: [PATCH 2/2] ARM: rdu2: fix dtc warning
Date: Tue, 13 Sep 2022 11:49:43 +0200 [thread overview]
Message-ID: <20220913094943.100107-2-s.hauer@pengutronix.de> (raw)
In-Reply-To: <20220913094943.100107-1-s.hauer@pengutronix.de>
This fixes:
dts/src/arm/imx6qdl.dtsi:1332.32-1334.7: Warning (graph_endpoint): /soc/ipu@2400000/port@2/endpoint@0: graph connection to node '/soc/bus@2100000/i2c@21a0000/edp-bridge@68/ports/port@1/endpoint' is not bidirectional
also defined at dts/src/arm/imx6qdl-zii-rdu2.dtsi:647.17-649.3
also defined at arch/arm/dts/imx6qdl-zii-rdu2.dtsi:246.17-248.3
dts/src/arm/imx6qdl-zii-rdu2.dtsi:186.25-188.6: Warning (graph_endpoint): /disp0/port@0/endpoint: graph connection to node '/soc/ipu@2400000/port@2/endpoint@0' is not bidirectional
dts/src/arm/imx6qdl.dtsi:1332.32-1334.7: Warning (graph_endpoint): /soc/ipu@2400000/port@2/endpoint@0: graph connection to node '/soc/bus@2100000/i2c@21a0000/edp-bridge@68/ports/port@1/endpoint' is not bidirectional
also defined at dts/src/arm/imx6qdl-zii-rdu2.dtsi:647.17-649.3
also defined at arch/arm/dts/imx6qdl-zii-rdu2.dtsi:246.17-248.3
dts/src/arm/imx6qdl-zii-rdu2.dtsi:186.25-188.6: Warning (graph_endpoint): /disp0/port@0/endpoint: graph connection to node '/soc/ipu@2400000/port@2/endpoint@0' is not bidirectional
I don't know if the link is non biderectional intentionally, it might
have something to do with the runtime dts adjustments. The warning
is around for a long time now without anybody caring, so just get
rid of it and see if somebody can explain the backgrounds or provide
a proper solution for it.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/dts/imx6qdl-zii-rdu2.dtsi | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm/dts/imx6qdl-zii-rdu2.dtsi b/arch/arm/dts/imx6qdl-zii-rdu2.dtsi
index 59f7656139..714ba8e755 100644
--- a/arch/arm/dts/imx6qdl-zii-rdu2.dtsi
+++ b/arch/arm/dts/imx6qdl-zii-rdu2.dtsi
@@ -243,10 +243,6 @@
};
};
-&ipu1_di0_disp0 {
- remote-endpoint = <&tc358767_in>;
-};
-
&ldb {
lvds-channel@0 {
fsl,data-width = <24>;
--
2.30.2
prev parent reply other threads:[~2022-09-13 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 9:49 [PATCH 1/2] ARM: rdu2: Drop redundant of graph link Sascha Hauer
2022-09-13 9:49 ` Sascha Hauer [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=20220913094943.100107-2-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=lst@pengutronix.de \
/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