From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-gpio@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 2/2] dt-bindings: pinctrl: use pinctrl.yaml
Date: Mon, 29 Nov 2021 14:49:03 -0600 [thread overview]
Message-ID: <YaU8v9WwVzDKbFa2@robh.at.kernel.org> (raw)
In-Reply-To: <20211110165720.30242-2-zajec5@gmail.com>
On Wed, 10 Nov 2021 17:57:20 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Also fix some examples to avoid warnings like:
> brcm,ns-pinmux.example.dt.yaml: pin-controller@1800c1c0: $nodename:0: 'pin-controller@1800c1c0' does not match '^pinctrl|pinmux@[0-9a-f]+$'
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../devicetree/bindings/pinctrl/actions,s500-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml | 1 +
> .../devicetree/bindings/pinctrl/apple,pinctrl.yaml | 3 +++
> .../bindings/pinctrl/aspeed,ast2400-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/aspeed,ast2500-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/aspeed,ast2600-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/brcm,bcm6318-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/brcm,bcm63268-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/brcm,bcm6328-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/brcm,bcm6358-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/brcm,bcm6362-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/brcm,bcm6368-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml | 3 ++-
> .../devicetree/bindings/pinctrl/canaan,k210-fpioa.yaml | 7 +++++--
> .../devicetree/bindings/pinctrl/cirrus,lochnagar.yaml | 3 +++
> .../devicetree/bindings/pinctrl/cirrus,madera.yaml | 3 +++
> .../devicetree/bindings/pinctrl/fsl,imx8mm-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/fsl,imx8mn-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/fsl,imx8mp-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/fsl,imx8mq-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/fsl,imx8ulp-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/ingenic,pinctrl.yaml | 8 ++++----
> .../devicetree/bindings/pinctrl/intel,lgm-io.yaml | 3 +++
> .../bindings/pinctrl/mediatek,mt65xx-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/mediatek,mt6779-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/mediatek,mt6797-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/mediatek,mt7622-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/mediatek,mt7986-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/mediatek,mt8183-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/pinctrl-mt8192.yaml | 3 +++
> .../devicetree/bindings/pinctrl/pinctrl-mt8195.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/qcom,lpass-lpi-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,mdm9607-pinctrl.yaml | 1 +
> .../devicetree/bindings/pinctrl/qcom,msm8226-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,msm8953-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,qcm2290-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,sc7280-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,sc8180x-pinctrl.yaml | 1 +
> .../devicetree/bindings/pinctrl/qcom,sdx55-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,sm6115-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,sm6125-pinctrl.yaml | 1 +
> .../devicetree/bindings/pinctrl/qcom,sm6350-pinctrl.yaml | 1 +
> .../devicetree/bindings/pinctrl/qcom,sm8250-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/qcom,sm8350-pinctrl.yaml | 1 +
> .../devicetree/bindings/pinctrl/qcom,tlmm-common.yaml | 3 +++
> .../devicetree/bindings/pinctrl/ralink,rt2880-pinmux.yaml | 3 +++
> .../devicetree/bindings/pinctrl/renesas,pfc.yaml | 3 +++
> .../devicetree/bindings/pinctrl/renesas,rza1-ports.yaml | 3 +++
> .../devicetree/bindings/pinctrl/renesas,rza2-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/renesas,rzg2l-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/renesas,rzn1-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/rockchip,pinctrl.yaml | 3 +++
> .../bindings/pinctrl/socionext,uniphier-pinctrl.yaml | 6 +++---
> .../devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml | 3 +++
> .../bindings/pinctrl/toshiba,visconti-pinctrl.yaml | 5 ++++-
> .../devicetree/bindings/pinctrl/xlnx,zynq-pinctrl.yaml | 3 +++
> .../devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml | 3 +++
> 58 files changed, 165 insertions(+), 11 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-11-29 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 16:57 [PATCH 1/2] dt-bindings: pinctrl: convert controller description to the json-schema Rafał Miłecki
2021-11-10 16:57 ` [PATCH 2/2] dt-bindings: pinctrl: use pinctrl.yaml Rafał Miłecki
2021-11-21 22:58 ` Linus Walleij
2021-11-29 20:49 ` Rob Herring [this message]
2021-12-02 2:01 ` Linus Walleij
2021-11-21 22:56 ` [PATCH 1/2] dt-bindings: pinctrl: convert controller description to the json-schema Linus Walleij
2021-11-29 20:45 ` Rob Herring
2021-12-02 2:00 ` 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=YaU8v9WwVzDKbFa2@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.