From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Frank Wunderlich <linux@fw-web.de>,
Rob Herring <robh+dt@kernel.org>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: Aw: Re: Re: Re: [PATCH v3 1/3] dt-bindings: Convert ahci-platform DT bindings to yaml
Date: Mon, 28 Feb 2022 18:06:12 +0100 [thread overview]
Message-ID: <22b1de71-a72a-ecb8-44a2-cf055d2a4fc5@canonical.com> (raw)
In-Reply-To: <trinity-bfe6b2d5-52cd-458d-92b2-66216620a4b3-1646067718759@3c-app-gmx-bs53>
On 28/02/2022 18:01, Frank Wunderlich wrote:
> Hi
>
>> Gesendet: Montag, 28. Februar 2022 um 15:35 Uhr
>> Von: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>
>>>> Gesendet: Montag, 28. Februar 2022 um 13:38 Uhr
>>>> Von: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>
>
>>>> No, this has to be oneOf. See for example
>>>> Documentation/devicetree/bindings/gpio/gpio-vf610.yaml or many other files.
>
>>> compatible:
>>> oneOf:
>>> - enum:
>>> - brcm,iproc-ahci
>>> - cavium,octeon-7130-ahci
>>> - hisilicon,hisi-ahci
>>> - ibm,476gtr-ahci
>>> - marvell,armada-3700-ahci
>>> - marvell,armada-380-ahci
>>> - snps,dwc-ahci
>>> - snps,spear-ahci
>>> - items:
>>> - const: generic-ahci
>>> - enum:
>>> - brcm,iproc-ahci
>>> - cavium,octeon-7130-ahci
>>> - hisilicon,hisi-ahci
>>> - ibm,476gtr-ahci
>>> - marvell,armada-3700-ahci
>>> - marvell,armada-380-ahci
>>> - snps,dwc-ahci
>>> - snps,spear-ahci
>>
>> That could be one way, but instead I propose to have only second part
>> (so enum + generic-ahci) for all compatibles mentioned in
>> ahci_platform.c, which do not customize the driver behavior for these
>> compatibles..
>
> tried many ways of defining it, but none passes with the examples. either to short (first example) or too long (second)
>
> as far as i understand the logic it should be similar to this:
>
> properties:
> compatible:
> oneOf:
> - items:
> - enum:
> - marvell,berlin2q-achi
You need to extend this enum with all the entries I mentioned before.
> - const: generic-ahci
> - items:
No items here, directly enum.
> - enum:
> - brcm,iproc-ahci
> - cavium,octeon-7130-ahci
> - hisilicon,hisi-ahci
> - ibm,476gtr-ahci
> - marvell,armada-3700-ahci
> - marvell,armada-380-ahci
> - snps,dwc-ahci
> - snps,spear-ahci
>
> this passes the dt-binding_check (examples) for me, but i guess there are many more compatibles defined with the generic.
>
> dtbs_check found some more like
>
> 'brcm,iproc-ahci'
> 'marvell,armada-8k-ahci'
> and many more
>
> it looks like these are also checked in the enum, so the yaml itself look correct, but needs some kind of wildcard instead of the "marvell,berlin2q-achi" as second for the generic-ahci compatible
>
> regards Frank
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-02-28 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 18:27 [PATCH v3 0/3] Add sata nodes to rk356x Frank Wunderlich
2022-02-27 18:27 ` [PATCH v3 1/3] dt-bindings: Convert ahci-platform DT bindings to yaml Frank Wunderlich
2022-02-28 10:08 ` Krzysztof Kozlowski
2022-02-28 12:19 ` Aw: " Frank Wunderlich
2022-02-28 12:38 ` Krzysztof Kozlowski
2022-02-28 14:09 ` Aw: " Frank Wunderlich
2022-02-28 14:35 ` Krzysztof Kozlowski
2022-02-28 17:01 ` Aw: " Frank Wunderlich
2022-02-28 17:06 ` Krzysztof Kozlowski [this message]
2022-02-27 18:27 ` [PATCH v3 2/3] dt-bindings: Add power-domains property to ahci-platform Frank Wunderlich
2022-02-28 10:09 ` Krzysztof Kozlowski
2022-02-27 18:28 ` [PATCH v3 3/3] arm64: dts: rockchip: Add sata nodes to rk356x Frank Wunderlich
2022-02-28 9:32 ` Johan Jonker
2022-02-28 9:54 ` 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=22b1de71-a72a-ecb8-44a2-cf055d2a4fc5@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=axboe@kernel.dk \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=hdegoede@redhat.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.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
all inboxes | Powered by JetHome®