From: Marek Vasut <marex@denx.de>
To: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>,
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>,
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
Subject: Re: [PATCH v3 3/3] ARM: dts: stm32: fix several DT warnings on stm32mp15
Date: Wed, 17 May 2023 17:41:54 +0200 [thread overview]
Message-ID: <f64de05b-8854-4345-80c2-f424968defdc@denx.de> (raw)
In-Reply-To: <20230517143542.284029-4-raphael.gallais-pou@foss.st.com>
On 5/17/23 16:35, Raphael Gallais-Pou wrote:
Hi,
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dkx.dtsi b/arch/arm/boot/dts/stm32mp15xx-dkx.dtsi
> index 0f1110e42c93..a6e2e20f12fa 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dkx.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dkx.dtsi
> @@ -457,8 +457,7 @@ <dc {
> status = "okay";
>
> port {
> - ltdc_ep0_out: endpoint@0 {
> - reg = <0>;
> + ltdc_ep0_out: endpoint {
> remote-endpoint = <&sii9022_in>;
> };
> };
This LTDC port/endpoint stuff always scares me, because I always feel I
get it wrong.
I believe the LTDC does have one "port" , correct.
But I think (?) that the LTDC has two endpoints, endpoint@0 for DPI
(parallel output out of the SoC) and endpoint@1 for DSI (internal
connection into the DSI serializer) ?
Only one of the endpoints can be connected at a time, but there are
actually two endpoints in the LTDC port {} node, aren't there ?
So the original description should be OK I think , maybe
#address/#size-cells are missing instead ?
next prev parent reply other threads:[~2023-05-17 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 14:35 [PATCH v3 0/3] STM32 warning cleanup Raphael Gallais-Pou
2023-05-17 14:35 ` [PATCH v3 1/3] ARM: dts: stm32: fix warnings on stm32f469-disco board Raphael Gallais-Pou
2023-05-26 16:55 ` Marek Vasut
2023-05-17 14:35 ` [PATCH v3 2/3] dt-bindings: display: st,stm32-dsi: Remove unnecessary fields Raphael Gallais-Pou
2023-05-17 17:30 ` Conor Dooley
2023-05-26 16:55 ` Marek Vasut
2023-05-17 14:35 ` [PATCH v3 3/3] ARM: dts: stm32: fix several DT warnings on stm32mp15 Raphael Gallais-Pou
2023-05-17 15:41 ` Marek Vasut [this message]
2023-05-17 17:04 ` Raphael Gallais-Pou
2023-05-17 23:33 ` Marek Vasut
2023-05-25 8:14 ` Raphael Gallais-Pou
2023-05-26 16:55 ` Marek Vasut
2023-05-29 8:07 ` Raphael Gallais-Pou
2023-05-29 9:49 ` Marek Vasut
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=f64de05b-8854-4345-80c2-f424968defdc@denx.de \
--to=marex@denx.de \
--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=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@foss.st.com \
--cc=raphael.gallais-pou@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;
as well as URLs for NNTP newsgroup(s).