From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-spi <linux-spi@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>, Mark Brown <broonie@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: spi: Add YAML schemas for the generic SPI options
Date: Thu, 16 May 2019 10:27:22 +0200 [thread overview]
Message-ID: <20190516082722.wcv2kmg4b5lqhszi@flea> (raw)
In-Reply-To: <CAL_JsqLRWSWk7cV=pYi1fbYsLJFUxE1fMo6Bm2FC99oPtS-88w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1434 bytes --]
Hi,
On Fri, May 10, 2019 at 11:05:48AM -0500, Rob Herring wrote:
> > +description: |
> > + SPI busses can be described with a node for the SPI controller device
> > + and a set of child nodes for each SPI slave on the bus. The system SPI
> > + controller may be described for use in SPI master mode or in SPI slave mode,
> > + but not for both at the same time.
> > +
> > +properties:
> > + $nodename:
> > + pattern: "^spi(@.*)$"
>
> Doing some testing with spi-gpio schema I'm writing, this needs to be
> "^spi(@.*)*$" so that just 'spi' is allowed.
I guess "^spi(@.*)+$" would be enough then?
> However, that's not enough for handling multiple instances of
> spi-gpio. So maybe we need "^spi(@.*|-[0-9a-f])*$" to allow spi-1,
> spi-2, etc. Really, we need to decide the larger issue of how we
> handle multiple instances when there's no address space.
That works for me, I'll change it.
> Also, this schema will be applied to any matching node name as it is
> used for automatic selection if compatible schema is not present. If
> we want to prevent that and only apply it when explicitly included,
> then we need to add a 'select: false'. Without it, we get more
> coverage, but it could slow things down and we'll get double printing
> of errors.
I guess we can change that later if it becomes too slow and / or
confusing?
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-16 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 7:26 [PATCH v2 1/4] dt-bindings: spi: Add YAML schemas for the generic SPI options Maxime Ripard
2019-05-09 7:26 ` [PATCH v2 2/4] dt-bindings: spi: sun4i: Add YAML schemas Maxime Ripard
2019-05-09 7:26 ` [PATCH v2 3/4] dt-bindings: spi: sun6i: " Maxime Ripard
2019-05-09 7:26 ` [PATCH v2 4/4] ARM: dts: sun6i: Add default address and size cells for SPI Maxime Ripard
2019-05-10 16:05 ` [PATCH v2 1/4] dt-bindings: spi: Add YAML schemas for the generic SPI options Rob Herring
2019-05-16 8:27 ` Maxime Ripard [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=20190516082722.wcv2kmg4b5lqhszi@flea \
--to=maxime.ripard@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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