From: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
To: Rob Herring <robh@kernel.org>
Cc: Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Lionel Debieve <lionel.debieve@foss.st.com>, <marex@denx.de>,
<linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] dt-bindings: rng: add st,stm32mp25-rng support
Date: Wed, 16 Oct 2024 09:49:27 +0200 [thread overview]
Message-ID: <6948f590-50ba-47d8-91b9-ee6f9d1ee31a@foss.st.com> (raw)
In-Reply-To: <20241015221740.GA2100600-robh@kernel.org>
On 10/16/24 00:17, Rob Herring wrote:
> On Tue, Oct 15, 2024 at 06:48:54PM +0200, Gatien Chevallier wrote:
>> Add RNG STM32MP25x platforms compatible. Update the clock
>> properties management to support all versions.
>>
>> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
>> ---
>> Changes in V3:
>> - Add constraint on clock-names for st,stm32mp25-rng compatible
>>
>> Changes in V2
>> -Fix missing min/maxItems
>> -Removed MP25 RNG example
>> -Renamed RNG clocks for mp25 to "core" and "bus"
>> ---
>> .../devicetree/bindings/rng/st,stm32-rng.yaml | 34 +++++++++++++++++++++-
>> 1 file changed, 33 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml b/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml
>> index 340d01d481d12ce8664a60db42182ddaf0d1385b..c276723d566ce4a0d6deca10c491510644d842f8 100644
>> --- a/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml
>> +++ b/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml
>> @@ -18,12 +18,20 @@ properties:
>> enum:
>> - st,stm32-rng
>> - st,stm32mp13-rng
>> + - st,stm32mp25-rng
>>
>> reg:
>> maxItems: 1
>>
>> clocks:
>> - maxItems: 1
>> + minItems: 1
>> + maxItems: 2
>> +
>> + clock-names:
>> + minItems: 1
>> + items:
>> + - const: core
>> + - const: bus
>>
>> resets:
>> maxItems: 1
>> @@ -57,6 +65,30 @@ allOf:
>> properties:
>> st,rng-lock-conf: false
>>
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - st,stm32-rng
>> + - st,stm32mp13-rng
>> + then:
>> + properties:
>> + clocks:
>> + maxItems: 1
>> + clock-names: false
>
> It makes no sense that you allowed 1 entry, but then disallow the
> property. Either drop the 'minItems: 1' at the top level (keeping this)
> or put 'maxItems: 1' here,
>
Hi Rob,
Will put maxItems: 1 here then.
>> + else:
>> + properties:
>> + clocks:
>> + minItems: 2
>> + maxItems: 2
>
> maxItems is already 2. Only need minItems.
>
Yes, will update for V4
>> + clock-names:
>> + items:
>> + - const: core
>> + - const: bus
>
> You already defined the names, don't do it again. You need either
> nothing or 'minItems: 2' depending on the above.
>
I will add minItems: 2 then, thanks!
>> + required:
>> + - clock-names
>> +
>> additionalProperties: false
>>
>> examples:
>>
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2024-10-16 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 16:48 [PATCH v3 0/4] Add support for stm32mp25x RNG Gatien Chevallier
2024-10-15 16:48 ` [PATCH v3 1/4] dt-bindings: rng: add st,stm32mp25-rng support Gatien Chevallier
2024-10-15 22:17 ` Rob Herring
2024-10-16 7:49 ` Gatien CHEVALLIER [this message]
2024-10-16 8:00 ` Gatien CHEVALLIER
2024-10-15 16:48 ` [PATCH v3 2/4] hwrng: stm32 - implement support for STM32MP25x platforms Gatien Chevallier
2024-10-15 16:57 ` Marek Vasut
2024-10-15 16:48 ` [PATCH v3 3/4] hwrng: stm32 - update STM32MP15 RNG max clock frequency Gatien Chevallier
2024-10-15 16:48 ` [PATCH v3 4/4] arm64: dts: st: add RNG node on stm32mp251 Gatien Chevallier
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=6948f590-50ba-47d8-91b9-ee6f9d1ee31a@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lionel.debieve@foss.st.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivia@selenic.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).