From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>, "Nuno Sa" <nuno.sa@analog.com>
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 2/4] ASoC: dt-bindings: document the adau1373 Codec
Date: Sat, 26 Oct 2024 20:14:10 +0200 [thread overview]
Message-ID: <e6f4b1b9-f860-4625-9f77-ee475235e958@kernel.org> (raw)
In-Reply-To: <a38c5d3e4f1cdf90f53b8c17ef7508faaf760f89.camel@gmail.com>
On 22/10/2024 08:42, Nuno Sá wrote:
>>> + $ref: /schemas/types.yaml#/definitions/uint8-array
>>> + oneOf:
>>> + - minItems: 13
>>> + - minItems: 26
>>> + - minItems: 39
>>
>> and maxItems?
>
> Hmm, I had the idea that if maxItems was omitted, then it's the same as
> minItems? Because that's the intent... We can either have an array of 13, 26 or
> 39 entries.
That's not the case and none of the files follow such logic. If you
manage to find one file, please correct or report it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-26 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 13:46 [PATCH 0/4] ASoC: codecs: adau1373: drop platform data Nuno Sa
2024-10-21 13:46 ` [PATCH 1/4] ASoC: codecs: adau1373: add some kconfig text Nuno Sa
2024-10-21 13:46 ` [PATCH 2/4] ASoC: dt-bindings: document the adau1373 Codec Nuno Sa
2024-10-22 6:06 ` Krzysztof Kozlowski
2024-10-22 6:42 ` Nuno Sá
2024-10-26 18:14 ` Krzysztof Kozlowski [this message]
2024-10-28 14:10 ` Nuno Sá
2024-10-21 13:46 ` [PATCH 3/4] ASoC: codecs: adau1373: drop patform_data Nuno Sa
2024-10-21 13:46 ` [PATCH 4/4] ASoC: codecs: adau1373: add powerdown gpio Nuno Sa
2024-10-21 15:30 ` Mark Brown
2024-10-22 6:39 ` Nuno Sá
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=e6f4b1b9-f860-4625-9f77-ee475235e958@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=nuno.sa@analog.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
/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