From: Michael Walle <michael@walle.cc>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Paul Burton <paulburton@kernel.org>,
Quentin Schulz <quentin.schulz@bootlin.com>,
Antoine Tenart <atenart@kernel.org>,
Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: "David S . Miller" <davem@davemloft.net>,
UNGLinuxDriver@microchip.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
Michael Walle <michael@walle.cc>
Subject: [PATCH v1 0/8] pinctrl: ocelot: convert to YAML format
Date: Sun, 13 Mar 2022 16:29:16 +0100 [thread overview]
Message-ID: <20220313152924.61931-1-michael@walle.cc> (raw)
Convert the pinctrl ocelot binding to the new YAML format. Pin
configuration nodes should have a "-pins" postfix. But unfortunately,
there are many device trees which don't follow this. First rename
all these nodes and then convert the binding to the YAML format so
that the validation will pass.
Because there were no maintainers before and there is none in
MAINTAINERS I added Alexandre Belloni and Lars Povlsen, juding by
the commits - to the binding as maintainers. Please tell me if you
disagree.
Michael Walle (8):
MIPS: mscc: jaguar2: fix pinctrl nodes
MIPS: mscc: ocelot: fix MIIM1 pinctrl node name
MIPS: mscc: ocelot: fix PHY interrupt pinctrl node name
MIPS: mscc: ocelot: fix load/save GPIO pinctrl name
MIPS: mscc: serval: fix pinctrl node names
arm64: dts: sparx5: fix pinctrl node names
ARM: dts: lan9662-pcb8291: fix pinctrl node name
dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format
.../bindings/pinctrl/mscc,ocelot-pinctrl.txt | 42 ---------
.../bindings/pinctrl/mscc,ocelot-pinctrl.yaml | 94 +++++++++++++++++++
arch/arm/boot/dts/lan966x-pcb8291.dts | 2 +-
.../dts/microchip/sparx5_pcb134_board.dtsi | 26 ++---
.../dts/microchip/sparx5_pcb135_board.dtsi | 10 +-
arch/mips/boot/dts/mscc/jaguar2_pcb110.dts | 10 +-
arch/mips/boot/dts/mscc/jaguar2_pcb111.dts | 10 +-
arch/mips/boot/dts/mscc/jaguar2_pcb118.dts | 6 +-
arch/mips/boot/dts/mscc/ocelot.dtsi | 4 +-
arch/mips/boot/dts/mscc/ocelot_pcb120.dts | 6 +-
arch/mips/boot/dts/mscc/serval_common.dtsi | 14 +--
11 files changed, 138 insertions(+), 86 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/pinctrl/mscc,ocelot-pinctrl.txt
create mode 100644 Documentation/devicetree/bindings/pinctrl/mscc,ocelot-pinctrl.yaml
--
2.30.2
next reply other threads:[~2022-03-13 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 15:29 Michael Walle [this message]
2022-03-13 15:29 ` [PATCH v1 1/8] MIPS: mscc: jaguar2: fix pinctrl nodes Michael Walle
2022-03-13 15:29 ` [PATCH v1 2/8] MIPS: mscc: ocelot: fix MIIM1 pinctrl node name Michael Walle
2022-03-13 15:29 ` [PATCH v1 3/8] MIPS: mscc: ocelot: fix PHY interrupt " Michael Walle
2022-03-13 15:29 ` [PATCH v1 4/8] MIPS: mscc: ocelot: fix load/save GPIO pinctrl name Michael Walle
2022-03-13 15:29 ` [PATCH v1 5/8] MIPS: mscc: serval: fix pinctrl node names Michael Walle
2022-03-13 15:29 ` [PATCH v1 6/8] arm64: dts: sparx5: " Michael Walle
2022-03-13 15:29 ` [PATCH v1 7/8] ARM: dts: lan9662-pcb8291: fix pinctrl node name Michael Walle
2022-03-13 15:29 ` [PATCH v1 8/8] dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format Michael Walle
2022-03-13 15:55 ` Krzysztof Kozlowski
2022-03-13 16:36 ` Michael Walle
2022-03-13 17:54 ` Krzysztof Kozlowski
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=20220313152924.61931-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lars.povlsen@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=paulburton@kernel.org \
--cc=quentin.schulz@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).