From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3] dt-bindings: pinctrl: sh-pfc: Convert to json-schema
Date: Fri, 28 Aug 2020 16:08:24 -0600 [thread overview]
Message-ID: <20200828220824.GA3490592@bogus> (raw)
In-Reply-To: <20200821112208.5295-1-geert+renesas@glider.be>
On Fri, 21 Aug 2020 13:22:08 +0200, Geert Uytterhoeven wrote:
> Convert the Renesas Pin Function Controller (PFC) Device Tree binding
> documentation to json-schema.
>
> Document missing properties.
> Drop deprecated and obsolete #gpio-range-cells property.
> Update the example to match reality.
> Drop consumer examples, as they do not belong here.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Notes:
> - "interrupts-extended" is used explicitly, because dt-schema does not
> apply the related fixup when "required: interrupts" is conditional,
> - "phandle: true" is needed because dt-schema does not add it
> automatically to subnodes.
>
> To be queued in sh-pfc for v5.10.
>
> v3:
> - Enable "drive-strength" and "power-source" enum checks, now
> dt-schema applies fixups correctly,
> - Refer to child schema instead of duplicating everything for
> grandchild nodes,
> - Use "pinctrl" generic node name,
> - Replace sh73a0 example by r8a7740 and r8a77951 examples,
> - Add child and grandchild example nodes to exercise all schema
> classes,
>
> v2:
> - Add missing "input" property for subnodes,
> - Rebase on top of:
> - "dt-bindings: pinctrl: sh-pfc: Document r8a7742 PFC support",
> - "dt-bindings: pinctrl: sh-pfc: Document r8a774e1 PFC support",
> - Describe pin configuration subnodes.
> ---
> .../bindings/pinctrl/renesas,pfc-pinctrl.txt | 188 -----------------
> .../bindings/pinctrl/renesas,pfc.yaml | 193 ++++++++++++++++++
> 2 files changed, 193 insertions(+), 188 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,pfc-pinctrl.txt
> create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,pfc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-08-28 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 11:22 [PATCH v3] dt-bindings: pinctrl: sh-pfc: Convert to json-schema Geert Uytterhoeven
2020-08-28 22:08 ` Rob Herring [this message]
2020-09-12 9:33 ` Linus Walleij
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=20200828220824.GA3490592@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@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).