From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Marek Vasut <marex@denx.de>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Yannick Fertre <yannick.fertre@foss.st.com>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@dh-electronics.com>,
Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
Subject: [PATCH v4 3/4] ARM: dts: stm32: fix dsi warnings on stm32mp15 boards
Date: Mon, 29 May 2023 11:13:58 +0200 [thread overview]
Message-ID: <20230529091359.71987-4-raphael.gallais-pou@foss.st.com> (raw)
In-Reply-To: <20230529091359.71987-1-raphael.gallais-pou@foss.st.com>
Fixes DSI related warnings:
* "#size-cells" and "#address-cells" wrongly used
* Changed 'panel-dsi@0' to 'panel@0' according to dsi-controller.yaml
Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
---
arch/arm/boot/dts/stm32mp157.dtsi | 7 -------
.../boot/dts/stm32mp157a-icore-stm32mp1-ctouch2-of10.dts | 3 +++
arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-edimm2.2.dts | 3 +++
arch/arm/boot/dts/stm32mp157c-dk2.dts | 5 +++++
arch/arm/boot/dts/stm32mp157c-ev1.dts | 7 ++++++-
5 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/arch/arm/boot/dts/stm32mp157.dtsi b/arch/arm/boot/dts/stm32mp157.dtsi
index 54e73ccea446..5e733cd16ff9 100644
--- a/arch/arm/boot/dts/stm32mp157.dtsi
+++ b/arch/arm/boot/dts/stm32mp157.dtsi
@@ -24,14 +24,7 @@ dsi: dsi@5a000000 {
clock-names = "pclk", "ref", "px_clk";
resets = <&rcc DSI_R>;
reset-names = "apb";
- #address-cells = <1>;
- #size-cells = <0>;
status = "disabled";
-
- ports {
- #address-cells = <1>;
- #size-cells = <0>;
- };
};
};
};
diff --git a/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-ctouch2-of10.dts b/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-ctouch2-of10.dts
index 9a2a4bc7d079..47d03bd9ef0b 100644
--- a/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-ctouch2-of10.dts
+++ b/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-ctouch2-of10.dts
@@ -49,6 +49,9 @@ &dsi {
phy-dsi-supply = <®18>;
ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
port@0 {
reg = <0>;
dsi_in: endpoint {
diff --git a/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-edimm2.2.dts b/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-edimm2.2.dts
index 390ee8c05754..d2f68997a471 100644
--- a/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-edimm2.2.dts
+++ b/arch/arm/boot/dts/stm32mp157a-icore-stm32mp1-edimm2.2.dts
@@ -49,6 +49,9 @@ &dsi {
phy-dsi-supply = <®18>;
ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
port@0 {
reg = <0>;
dsi_in_ltdc: endpoint {
diff --git a/arch/arm/boot/dts/stm32mp157c-dk2.dts b/arch/arm/boot/dts/stm32mp157c-dk2.dts
index ab13e340f4ef..0067c6248cd1 100644
--- a/arch/arm/boot/dts/stm32mp157c-dk2.dts
+++ b/arch/arm/boot/dts/stm32mp157c-dk2.dts
@@ -31,10 +31,15 @@ &cryp1 {
};
&dsi {
+ #address-cells = <1>;
+ #size-cells = <0>;
status = "okay";
phy-dsi-supply = <®18>;
ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
port@0 {
reg = <0>;
dsi_in: endpoint {
diff --git a/arch/arm/boot/dts/stm32mp157c-ev1.dts b/arch/arm/boot/dts/stm32mp157c-ev1.dts
index ba8e9d9a42fa..67c6b9440878 100644
--- a/arch/arm/boot/dts/stm32mp157c-ev1.dts
+++ b/arch/arm/boot/dts/stm32mp157c-ev1.dts
@@ -101,9 +101,14 @@ dcmi_0: endpoint {
&dsi {
phy-dsi-supply = <®18>;
+ #address-cells = <1>;
+ #size-cells = <0>;
status = "okay";
ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
port@0 {
reg = <0>;
dsi_in: endpoint {
@@ -119,7 +124,7 @@ dsi_out: endpoint {
};
};
- panel-dsi@0 {
+ panel@0 {
compatible = "raydium,rm68200";
reg = <0>;
reset-gpios = <&gpiof 15 GPIO_ACTIVE_LOW>;
--
2.25.1
next prev parent reply other threads:[~2023-05-29 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 9:13 [PATCH v4 0/4] STM32 warning cleanup Raphael Gallais-Pou
2023-05-29 9:13 ` [PATCH v4 1/4] ARM: dts: stm32: fix warnings on stm32f469-disco board Raphael Gallais-Pou
2023-05-29 9:13 ` [PATCH v4 2/4] dt-bindings: display: st,stm32-dsi: Remove unnecessary fields Raphael Gallais-Pou
2023-05-30 12:27 ` Krzysztof Kozlowski
2023-05-30 13:30 ` Alexandre TORGUE
2023-05-30 13:38 ` Raphael Gallais-Pou
2023-05-30 15:13 ` Krzysztof Kozlowski
2023-05-29 9:13 ` Raphael Gallais-Pou [this message]
2023-05-29 9:51 ` [PATCH v4 3/4] ARM: dts: stm32: fix dsi warnings on stm32mp15 boards Marek Vasut
2023-05-29 9:13 ` [PATCH v4 4/4] ARM: dts: stm32: fix ltdc warnings in " Raphael Gallais-Pou
2023-05-29 9:54 ` Marek Vasut
2023-05-30 8:19 ` [PATCH v4 0/4] STM32 warning cleanup Alexandre TORGUE
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=20230529091359.71987-4-raphael.gallais-pou@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@dh-electronics.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@foss.st.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@foss.st.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
all inboxes | Powered by JetHome®