From: Andre Przywara <andre.przywara@arm.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Icenowy Zheng <icenowy@aosc.xyz>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@googlegroups.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: spi: sunxi: Document new compatible strings
Date: Thu, 16 Jan 2020 14:38:09 +0000 [thread overview]
Message-ID: <20200116143809.123ceee4@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <20200116142301.w2t4o6pg3dapp3g6@gilmour.lan>
On Thu, 16 Jan 2020 15:23:01 +0100
Maxime Ripard <mripard@kernel.org> wrote:
Hi,
> On Thu, Jan 16, 2020 at 12:56:54AM +0000, Andre Przywara wrote:
> > The Allwinner H6 SPI controller has advanced features over the H3
> > version, but remains compatible with it.
> > Document the usual "specific", "fallback" compatible string pair.
> > Also add the R40 version while at it.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> > ---
> > .../devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml | 12 +++++++++---
> > 1 file changed, 9 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml
> > index f36c46d236d7..c19dfbe42d90 100644
> > --- a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml
> > +++ b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml
> > @@ -18,9 +18,15 @@ properties:
> > "#size-cells": true
> >
> > compatible:
> > - enum:
> > - - allwinner,sun6i-a31-spi
> > - - allwinner,sun8i-h3-spi
> > + oneOf:
> > + - const: allwinner,sun6i-a31-spi
> > + - const: allwinner,sun8i-h3-spi
> > + - items:
> > + - const: allwinner,sun8i-r40-spi
> > + - const: allwinner,sun8i-h3-spi
> > + - items:
> > + - const: allwinner,sun50i-h6-spi
> > + - const: allwinner,sun8i-h3-spi
>
> Having
>
> oneOf:
> - const: allwinner,sun6i-a31-spi
> - const: allwinner,sun8i-h3-spi
> - items:
> - enum:
> - allwinner,sun8i-r40-spi
> - allwinner,sun50i-h6-spi
> - const: allwinner,sun8i-h3-spi
>
> Will be easier to maintain in the long run
Ah, nice, I tried something like this, based on the example-schema.yaml file, but the example in there is more verbose, and looked much less readable.
But your version seems to hit the sweet spot, so I will go with this.
Thanks,
Andre.
prev parent reply other threads:[~2020-01-16 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 0:56 [PATCH v2 0/3] arm64: dts: sun50i: H6: Enable SPI controller Andre Przywara
2020-01-16 0:56 ` [PATCH v2 1/3] arm64: dts: sun50i: H6: Add SPI controllers nodes and pinmuxes Andre Przywara
2020-01-16 0:56 ` [PATCH v2 2/3] arm64: dts: allwinner: h6: Pine H64: Add SPI flash node Andre Przywara
2020-01-16 0:56 ` [PATCH v2 3/3] dt-bindings: spi: sunxi: Document new compatible strings Andre Przywara
2020-01-16 14:23 ` Maxime Ripard
2020-01-16 14:38 ` Andre Przywara [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=20200116143809.123ceee4@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).