From: Tony Lindgren <tony@atomide.com>
To: Rob Herring <robh@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: Update pinctrl-single to use yaml
Date: Mon, 16 Jan 2023 13:15:19 +0200 [thread overview]
Message-ID: <Y8UxxwdbiHdJ7WF+@atomide.com> (raw)
In-Reply-To: <20230113202016.GA2833245-robh@kernel.org>
Hi Rob,
I ran into error "is not of type 'object'" with two dashes in the property
name.
* Rob Herring <robh@kernel.org> [230113 20:20]:
> On Thu, Jan 12, 2023 at 10:31:50AM +0200, Tony Lindgren wrote:
> > -- #pinctrl-single,gpio-range-cells : the number of parameters after phandle in
> > - pinctrl-single,gpio-range property.
> > -
> > - range: gpio-range {
> > - #pinctrl-single,gpio-range-cells = <3>;
> > - };
>
> You've lost describing this.
Thanks for noticing. Adding something like below produces errors for the
pinctrl-single,gpio-range property name:
pinctrl-single,gpio-range:
description: Optional list of pin base, nr pins & gpio function
$ref: /schemas/types.yaml#/definitions/phandle-array
items:
- items:
- description: phandle of a gpio-range node
- description: pin base
- description: number of pins
- description: gpio function
pinctrl-single,gpio-range = <&range 0 3 0>;
The error is:
pinctrl-single.example.dtb: pinmux@4a100040: pinctrl-single,gpio-range:
[[1, 0, 3, 0]] is not of type 'object'
Changing the property name second dash to something else makes it go away.
This is with dtschema 2022.12. Any ideas?
Regards,
Tony
prev parent reply other threads:[~2023-01-16 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 8:31 [PATCH] dt-bindings: pinctrl: Update pinctrl-single to use yaml Tony Lindgren
2023-01-12 20:18 ` kernel test robot
2023-01-13 6:06 ` Tony Lindgren
2023-01-13 20:20 ` Rob Herring
2023-01-16 6:49 ` Tony Lindgren
2023-01-16 11:15 ` Tony Lindgren [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=Y8UxxwdbiHdJ7WF+@atomide.com \
--to=tony@atomide.com \
--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=robh@kernel.org \
--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).