From: "André Draszik" <andre.draszik@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: Will McVicker <willmcvicker@google.com>,
kernel-team@android.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: google: add gs101-raven and generic gs101-pixel
Date: Mon, 23 Dec 2024 15:54:17 +0000 [thread overview]
Message-ID: <34f62a976e4dd2d56eb34e4efa987ddc3e2f31ca.camel@linaro.org> (raw)
In-Reply-To: <c2efb6c7-4a0b-4078-b0df-6e646eb88906@kernel.org>
On Mon, 2024-12-23 at 16:39 +0100, Krzysztof Kozlowski wrote:
> On 23/12/2024 16:31, André Draszik wrote:
> > On Mon, 2024-12-23 at 15:14 +0100, Krzysztof Kozlowski wrote:
> >
> > >
> > > You now say that these are valid boards:
> > >
> > > compatible = "google,gs101", "google,gs101";
> >
> > Sorry, I don't see how (apart from the fact that dtbs_check flags
> > non-unique elements anyway). The result of the patch is:
> >
> > minItems: 2
> > maxItems: 3
> > items:
> > enum:
> > - google,gs101-oriole
> > - google,gs101-raven
> > - google,gs101-pixel
> > - google,gs101
>
> The problem is this line. Although entire concept of flexible list is
> neither need nor ever recommended.
All of this was inspired by Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
I guess not a good example in this case...
>
> > allOf:
> > - contains:
> > const: google,gs101-pixel
> > - contains:
> > const: google,gs101
> >
> > So one can not have 'google,gs101' twice. And if I only add
>
> Still can be, but indeed not with my example but:
>
> "google,gs101", "google,gs101", "google,gs101-pixel";
This example doesn't pass irrespective of binding, because
dtbs_check will complain about non-unique elements.
Anyway, will use separate entries.
Thanks Krzysztof,
Cheers,
Andre'
>
next prev parent reply other threads:[~2024-12-23 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 11:27 [PATCH v2 0/3] Google Pixel 6 Pro support André Draszik
2024-12-20 11:27 ` [PATCH v2 1/3] dt-bindings: arm: google: add gs101-raven and generic gs101-pixel André Draszik
2024-12-22 11:38 ` Krzysztof Kozlowski
2024-12-23 7:45 ` André Draszik
2024-12-23 14:14 ` Krzysztof Kozlowski
2024-12-23 15:31 ` André Draszik
2024-12-23 15:39 ` Krzysztof Kozlowski
2024-12-23 15:54 ` André Draszik [this message]
2024-12-23 15:58 ` Krzysztof Kozlowski
2024-12-20 11:27 ` [PATCH v2 2/3] arm64: dts: exynos: gs101-pixel: add generic gs101-based Pixel support André Draszik
2024-12-22 11:42 ` Krzysztof Kozlowski
2024-12-23 7:59 ` André Draszik
2024-12-23 14:18 ` Krzysztof Kozlowski
2024-12-20 11:27 ` [PATCH v2 3/3] arm64: dts: exynos: gs101-raven: add new board file André Draszik
2024-12-22 11:43 ` Krzysztof Kozlowski
2024-12-23 10:42 ` André Draszik
2024-12-20 14:42 ` [PATCH v2 0/3] Google Pixel 6 Pro support André Draszik
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=34f62a976e4dd2d56eb34e4efa987ddc3e2f31ca.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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;
as well as URLs for NNTP newsgroup(s).