From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Imre Kaloz <kaloz@openwrt.org>,
Krzysztof Halasa <khalasa@piap.pl>, Marc Zyngier <maz@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] bus: ixp4xx: Add DT bindings for the IXP4xx expansion bus
Date: Tue, 20 Jul 2021 10:39:05 -0600 [thread overview]
Message-ID: <CAL_JsqLrw6Y+aMYRFF87E=X2tvyF_OUn7OkzLVUS7WvGAbehvA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbmdd9TuVD-Lanme77-0XKg0up3jrXeisYNR4p9EL=9kQ@mail.gmail.com>
On Mon, Jul 19, 2021 at 4:49 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Mon, Jul 19, 2021 at 5:18 PM Rob Herring <robh@kernel.org> wrote:
>
> > > +patternProperties:
> > > + "^.*@[0-7],[0-9a-f]+$":
> > > + description: Devices attached to chip selects are represented as
> > > + subnodes.
> > > + type: object
> > > +
> > > + properties:
> > > + intel,ixp4xx-eb-t1:
> > > + description: Address timing, extend address phase with n cycles.
> > > + $ref: /schemas/types.yaml#/definitions/uint32
> > > + maximum: 3
>
> (...)
>
> > > + unevaluatedProperties: false
> >
> > This will cause failures when implemented. The problem is this won't
> > allow any other child node properties as this schema and the device
> > schema are evaluated independently. The only way I see to solve this is
> > the child node schemas have to include some 'bus properties' schema
> > which includes all possible bus controller properties. There's been a
> > recent patch set doing this for SPI. At least here, I think the number
> > of different child devices on parallel expansion buses are limited.
> >
> > So spliting this to 2 schema files would be the first step. Minimally,
> > just drop unevaluatedProperties.
>
> SPI upstream simply uses
>
> additionalProperties: true
>
> is that acceptable for now?
Yes. (That is the default)
Rob
prev parent reply other threads:[~2021-07-20 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 0:16 [PATCH 1/2] bus: ixp4xx: Add DT bindings for the IXP4xx expansion bus Linus Walleij
2021-07-19 13:47 ` Rob Herring
2021-07-19 14:10 ` Linus Walleij
2021-07-19 15:18 ` Rob Herring
2021-07-19 22:48 ` Linus Walleij
2021-07-20 16:39 ` Rob Herring [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='CAL_JsqLrw6Y+aMYRFF87E=X2tvyF_OUn7OkzLVUS7WvGAbehvA@mail.gmail.com' \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kaloz@openwrt.org \
--cc=khalasa@piap.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@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;
as well as URLs for NNTP newsgroup(s).