From: Marek Vasut <marex@denx.de>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>,
Alexandre TORGUE <alexandre.torgue@foss.st.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Pascal Paillet <p.paillet@foss.st.com>
Cc: 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 v3 1/2] dt-bindings: regulator: st,stm32mp1-pwr-reg: add compatible for STM32MP13
Date: Mon, 13 May 2024 16:34:20 +0200 [thread overview]
Message-ID: <615dfdcb-cbda-426f-895e-810f03a8ce60@denx.de> (raw)
In-Reply-To: <20240513115601.v3.1.Ia0a99d90acb512aa020a6e7a8cca8cc1b71f1759@changeid>
On 5/13/24 11:56 AM, Patrick Delaunay wrote:
> Add new compatible "st,stm32mp13-pwr-reg" for STM32MP13 SoC family.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> ---
>
> Changes in v3:
> - Replace oneOf/const by enum; solve the V2 issues for dt_binding_check
>
> Changes in v2:
> - update for Rob review, only add compatible for STM32MP13 family
>
> .../devicetree/bindings/regulator/st,stm32mp1-pwr-reg.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/regulator/st,stm32mp1-pwr-reg.yaml b/Documentation/devicetree/bindings/regulator/st,stm32mp1-pwr-reg.yaml
> index c9586d277f41..c766f0a15a31 100644
> --- a/Documentation/devicetree/bindings/regulator/st,stm32mp1-pwr-reg.yaml
> +++ b/Documentation/devicetree/bindings/regulator/st,stm32mp1-pwr-reg.yaml
> @@ -11,7 +11,9 @@ maintainers:
>
> properties:
> compatible:
> - const: st,stm32mp1,pwr-reg
> + enum:
> + - st,stm32mp1,pwr-reg
> + - st,stm32mp13-pwr-reg
Should the st,stm32mp1,pwr-reg be treated as fallback compatible for
st,stm32mp13-pwr-reg or not ?
In other words, should the DT contain:
compatible = "st,stm32mp13-pwr-reg", "st,stm32mp1,pwr-reg";
or
compatible = "st,stm32mp13-pwr-reg";
? Which one is preferable ?
I think the former one, since the MP13 PWR block could also be operated
by older MP1(5) PWR block driver(s) without any adverse effects, except
the SD IO domain configuration won't be available, right ?
next prev parent reply other threads:[~2024-05-13 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 9:56 [PATCH v3 0/2] ARM: st: add new compatible for PWR regulators on STM32MP13 Patrick Delaunay
2024-05-13 9:56 ` [PATCH v3 1/2] dt-bindings: regulator: st,stm32mp1-pwr-reg: add compatible for STM32MP13 Patrick Delaunay
2024-05-13 14:34 ` Marek Vasut [this message]
2024-05-13 15:16 ` Conor Dooley
2024-05-13 18:02 ` Patrick DELAUNAY
2024-05-14 20:08 ` Conor Dooley
2024-05-15 14:33 ` Patrick DELAUNAY
2024-05-15 15:35 ` Conor Dooley
2024-05-15 15:37 ` Marek Vasut
2024-05-15 16:15 ` Conor Dooley
2024-05-16 16:32 ` 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=615dfdcb-cbda-426f-895e-810f03a8ce60@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@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=p.paillet@foss.st.com \
--cc=patrick.delaunay@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).