From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: Marek Vasut <marex@denx.de>,
<linux-arm-kernel@lists.infradead.org>,
Philippe CORNU - foss <philippe.cornu@foss.st.com>,
yannick Fertre <yannick.fertre@foss.st.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] ARM: dts: stm32: Deduplicate DSI node
Date: Fri, 9 Jun 2023 16:17:26 +0200 [thread overview]
Message-ID: <2d13447a-bcdb-36d2-f988-b1f416244e1d@foss.st.com> (raw)
In-Reply-To: <94a89ca7-bc29-5a2e-f99d-9b2577882c92@denx.de>
Hi Marek,
On 6/1/23 22:32, Marek Vasut wrote:
> On 6/1/23 18:46, Raphael Gallais-Pou wrote:
>> Hi Marek,
>
> Hi,
>
>> On 6/1/23 01:10, Marek Vasut wrote:
>>> All boards using the DSI node duplicate the same pattern common pattern
>>> in board DTs, that pattern is ports with endpoint labels and the same
>>> in-SoC regulator connection. Move that common pattern into stm32mp157.dtsi
>>> instead.
>>
>> I think that is a good idea, while it did not crossed my mind implementing it
>> this way on the first time.
>>
>> I'll let my peers Philippe and Yannick review and ack it this time. I tested it
>> on DK2, it seems fine.
>
> Thanks for testing. There's no rush, so take your time.
Acked-by: Raphaël Gallais-Pou <raphael.gallais-pou@foss.st.com>
Thank you,
Raphaël
next prev parent reply other threads:[~2023-06-09 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 23:10 [PATCH] ARM: dts: stm32: Deduplicate DSI node Marek Vasut
2023-06-01 16:46 ` Raphael Gallais-Pou
2023-06-01 20:32 ` Marek Vasut
2023-06-09 14:17 ` Raphael Gallais-Pou [this message]
2023-07-11 9:01 ` 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=2d13447a-bcdb-36d2-f988-b1f416244e1d@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).