From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Rob Herring <robh@kernel.org>
Cc: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Pascal Paillet <p.paillet@foss.st.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 0/3] ARM: st: use a correct pwr compatible for stm32mp15
Date: Fri, 26 Apr 2024 13:41:12 +0200 [thread overview]
Message-ID: <28aeb8b1-72f1-4dd9-b433-f5b693150475@foss.st.com> (raw)
In-Reply-To: <20240425163035.GA2783061-robh@kernel.org>
Hi,
On 4/25/24 18:30, Rob Herring wrote:
> On Thu, Apr 25, 2024 at 09:48:31AM +0200, Patrick Delaunay wrote:
>> This patchset removes the unexpected comma in the PWR compatible
>> "st,stm32mp1,pwr-reg" and uses a new compatible "st,stm32mp1-pwr-reg"
>> in STM3MP15 device trees.
> Why? I don't see any warnings from this. Yes, we wouldn't new cases
> following this pattern, but I don't think it is worth maintaining
> support for both strings. We're stuck with it. And the only way to
> maintain forward compatibility is:
Yes, no warning because the compatible string are not yet checked by tools.
I propose this patch to avoid the usage of this compatible for other SoC
in STM32MP1 family.
I see the invalid compatible string when I reviewed the U-Boot patch to
add the PWR node for STM32MP13 family:
https://patchwork.ozlabs.org/project/uboot/patch/20240319024534.103299-1-marex@denx.de/
So I prefer change the PWR binding before to have the same patch applied
on Linux device tree
> compatible = "st,stm32mp1-pwr-reg", "st,stm32mp1,pwr-reg";
Yes, I will update the SoC patch with you proposal.
it is the only way to have compatibility of OLD Linux kernel (with old
driver) with NEW device tree.
I miss this compatibility issue.
>
> Rob
>
>
>
Regards
Patrick
next prev parent reply other threads:[~2024-04-26 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 7:48 [PATCH 0/3] ARM: st: use a correct pwr compatible for stm32mp15 Patrick Delaunay
2024-04-25 7:48 ` [PATCH 1/3] dt-bindings: regulator: st,stm32mp1-pwr-reg: add correct compatible Patrick Delaunay
2024-04-25 8:52 ` Krzysztof Kozlowski
2024-04-25 13:55 ` Patrick DELAUNAY
2024-04-25 7:48 ` [PATCH 3/3] ARM: dts: st: update the pwr compatible for stm32mp15 Patrick Delaunay
2024-04-25 8:57 ` Krzysztof Kozlowski
2024-04-25 13:54 ` Patrick DELAUNAY
2024-04-25 16:30 ` [PATCH 0/3] ARM: st: use a correct " Rob Herring
2024-04-26 11:41 ` Patrick DELAUNAY [this message]
2024-04-26 12:51 ` Rob Herring
2024-04-26 14:28 ` Patrick DELAUNAY
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=28aeb8b1-72f1-4dd9-b433-f5b693150475@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--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=olivier.moysan@foss.st.com \
--cc=p.paillet@foss.st.com \
--cc=robh@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).