From: Rob Herring <robh@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Nishanth Menon <nm@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v3 1/1] dt-bindings: pinctrl: Update pinctrl-single to use yaml
Date: Tue, 17 Jan 2023 14:04:37 -0600 [thread overview]
Message-ID: <20230117200437.GA3538302-robh@kernel.org> (raw)
In-Reply-To: <Y8WFIzElz8/pv4uy@atomide.com>
On Mon, Jan 16, 2023 at 07:10:59PM +0200, Tony Lindgren wrote:
> * Rob Herring <robh+dt@kernel.org> [230116 16:39]:
> > I imagine you don't want to go change all these node names, so I'd
> > make the schema accept them.
>
> Heh yeah, I was wondering about that too :) Some can be handled with a
> regex, but there are still a lot of completely custom names. If you have
> some preferred solution in mind, please let me know.
If just allowing 'pins' anywhere in the name is not enough, you can
match on any other property with 'additionalProperties'. There's some
examples in pinctrl bindings.
additionalProperties:
type: object
properties:
...
Or use 'unevaluatedProperties' if there's properties defined behind a
$ref.
There's also this hack, but I try to avoid it:
patternProperties:
'.*':
if:
type: object
then:
...
Rob
next prev parent reply other threads:[~2023-01-17 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 7:15 [PATCH v3 1/1] dt-bindings: pinctrl: Update pinctrl-single to use yaml Tony Lindgren
2023-01-16 7:27 ` Tony Lindgren
2023-01-16 16:36 ` Rob Herring
2023-01-16 16:38 ` Rob Herring
2023-01-16 17:10 ` Tony Lindgren
2023-01-17 20:04 ` Rob Herring [this message]
2023-02-10 8:30 ` Andreas Kemnade
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=20230117200437.GA3538302-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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).