From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
devicetree@vger.kernel.org
Cc: Hartley Sweeten <hsweeten@visionengravers.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: sound: ep93xx: Add I2S and AC'97 descriptions
Date: Wed, 15 Feb 2023 20:19:42 +0100 [thread overview]
Message-ID: <2334035b-cc52-8dfb-9ba4-544081b98d6f@linaro.org> (raw)
In-Reply-To: <ba51ecefb814115e977d90062ca5fe99859cb327.camel@gmail.com>
On 14/02/2023 15:26, Alexander Sverdlin wrote:
> Hello Krzysztof!
>
> On Tue, 2023-02-14 at 15:11 +0100, Krzysztof Kozlowski wrote:
>>>>> + interrupts:
>>>>> + maxItems: 1
>>>>> +
>>>>> + clocks:
>>>>> + minItems: 3
>>>>
>>>> maxItems instead
>>>
>>> reg and clocks are required, I suppose I should include both minItems
>>> and maxItems for both of them?
>>
>> No. minItems is implied.
>
> I see. But I think minItems "3" should be included for clocks, right?
No, why? It is implied when you provide maxItems. Therefore why would
you need it to make it explicitly (although you can, but we avoid it for
smaller code)?
Best regards,
Krzysztof
prev parent reply other threads:[~2023-02-15 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 23:21 [PATCH 1/2] dt-bindings: sound: ep93xx: Add I2S and AC'97 descriptions Alexander Sverdlin
2023-02-12 23:21 ` [PATCH 2/2] ASoC: ep93xx: Add OF support Alexander Sverdlin
2023-02-14 10:58 ` [PATCH 1/2] dt-bindings: sound: ep93xx: Add I2S and AC'97 descriptions Krzysztof Kozlowski
2023-02-14 13:02 ` Alexander Sverdlin
2023-02-14 14:11 ` Krzysztof Kozlowski
2023-02-14 14:26 ` Alexander Sverdlin
2023-02-14 15:02 ` Mark Brown
2023-02-15 19:16 ` Rob Herring
2023-02-15 19:19 ` Krzysztof Kozlowski [this message]
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=2334035b-cc52-8dfb-9ba4-544081b98d6f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexander.sverdlin@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hsweeten@visionengravers.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).