From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: sboyd@kernel.org, abelvesa@kernel.org, hs@denx.de,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@denx.de>
Subject: [PATCH v2 1/3] ARM: dts: imx6sx: Remove LDB endpoint
Date: Fri, 9 Jun 2023 00:12:47 -0300 [thread overview]
Message-ID: <20230609031249.3692841-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@denx.de>
Remove the LDB endpoint description from the common imx6sx.dtsi
as it causes regression for boards that has the LCDIF connected
directly to a parallel display.
Let the LDB endpoint be described in the board devicetree file
instead.
Fixes: b74edf626c4f ("ARM: dts: imx6sx: Add LDB support")
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v1:
- None
arch/arm/boot/dts/imx6sx.dtsi | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/imx6sx.dtsi b/arch/arm/boot/dts/imx6sx.dtsi
index 3a4308666552..41c900929758 100644
--- a/arch/arm/boot/dts/imx6sx.dtsi
+++ b/arch/arm/boot/dts/imx6sx.dtsi
@@ -863,7 +863,6 @@ port@0 {
reg = <0>;
ldb_from_lcdif1: endpoint {
- remote-endpoint = <&lcdif1_to_ldb>;
};
};
@@ -1309,11 +1308,8 @@ lcdif1: lcdif@2220000 {
power-domains = <&pd_disp>;
status = "disabled";
- ports {
- port {
- lcdif1_to_ldb: endpoint {
- remote-endpoint = <&ldb_from_lcdif1>;
- };
+ port {
+ lcdif1_to_ldb: endpoint {
};
};
};
--
2.34.1
next reply other threads:[~2023-06-09 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 3:12 Fabio Estevam [this message]
2023-06-09 3:12 ` [PATCH v2 2/3] ARM: dts: imx6sx: Describe the default LCDIF1 parent Fabio Estevam
2023-06-09 3:12 ` [PATCH v2 3/3] clk: imx: imx6sx: Allow passing the LCDIF1 parent via DT Fabio Estevam
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=20230609031249.3692841-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=abelvesa@kernel.org \
--cc=festevam@denx.de \
--cc=hs@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).