From: Valentin CARON <valentin.caron@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: serial: stm32: add power-domains property
Date: Wed, 17 Jan 2024 10:21:11 +0100 [thread overview]
Message-ID: <1639c6b9-1cca-4f4c-a329-fc4618c572f6@foss.st.com> (raw)
In-Reply-To: <aae32b47-1bb0-4af0-baf0-836dc91b9427@linaro.org>
On 1/15/24 16:05, Krzysztof Kozlowski wrote:
> On 11/01/2024 12:24, Valentin Caron wrote:
>> Add "power-domains" property in stm32 serial binding to avoid:
>>
>> serial@40010000: Unevaluated properties are not allowed
>> ('power-domains' were unexpected)
>>
> It would be better if you checked whether it can be part of power domain
> or not. What if the DTS is wrong?
>
> Best regards,
> Krzysztof
>
Hi Krzysztof,
I'm not sure to understand, but if you mean that there is no
power-domains properties right now in all stm32mp device trees
and so it does not required to add this stm32 serial bindings:
Theses will be upstreamed in the future, and because power-domains
property is optional, I can add it right now in stm32 serial binding
to anticipate.
Best regards,
Valentin
next prev parent reply other threads:[~2024-01-17 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 11:24 [PATCH] dt-bindings: serial: stm32: add power-domains property Valentin Caron
2024-01-15 15:05 ` Krzysztof Kozlowski
2024-01-17 9:21 ` Valentin CARON [this message]
2024-01-17 9:23 ` Krzysztof Kozlowski
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=1639c6b9-1cca-4f4c-a329-fc4618c572f6@foss.st.com \
--to=valentin.caron@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=robh+dt@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).