From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: ulf.hansson@linaro.org, robh+dt@kernel.org, krzk+dt@kernel.org,
andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com, adrian.hunter@intel.com,
nico@fluxnic.net
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v2 0/4] dt-bindings: mmc: Convert orion/dove bindings to JSON schema
Date: Tue, 19 Apr 2022 14:46:07 +1200 [thread overview]
Message-ID: <20220419024611.1327525-1-chris.packham@alliedtelesis.co.nz> (raw)
This is a small series converting the device tree bindings for the orion and
dove sdhci controllers to JSON schema.
The first 2 patches update the dtsi files to use a node name enforces by the
schema. These need to be applied for the schema to validate correctly.
The next 2 patches convert the old text binding to JSON schema.
Chris Packham (4):
ARM: dts: mvebu: Update mvsdio node names to match schema
ARM: dts: dove: Update sdio-host node names to match schema
dt-bindings: mmc: convert orion-sdio to JSON schema
dt-bindings: mmc: convert sdhci-dove to JSON schema
.../bindings/mmc/marvell,dove-sdhci.yaml | 44 +++++++++++++++++++
.../bindings/mmc/marvell,orion-sdio.yaml | 44 +++++++++++++++++++
.../devicetree/bindings/mmc/orion-sdio.txt | 16 -------
.../devicetree/bindings/mmc/sdhci-dove.txt | 14 ------
arch/arm/boot/dts/armada-370-xp.dtsi | 2 +-
arch/arm/boot/dts/armada-375.dtsi | 2 +-
arch/arm/boot/dts/dove.dtsi | 4 +-
arch/arm/boot/dts/kirkwood-6192.dtsi | 2 +-
arch/arm/boot/dts/kirkwood-6281.dtsi | 2 +-
arch/arm/boot/dts/kirkwood-6282.dtsi | 2 +-
10 files changed, 95 insertions(+), 37 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mmc/marvell,dove-sdhci.yaml
create mode 100644 Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml
delete mode 100644 Documentation/devicetree/bindings/mmc/orion-sdio.txt
delete mode 100644 Documentation/devicetree/bindings/mmc/sdhci-dove.txt
--
2.35.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-19 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 2:46 Chris Packham [this message]
2022-04-19 2:46 ` [PATCH v2 1/4] ARM: dts: mvebu: Update mvsdio node names to match schema Chris Packham
2022-04-19 12:08 ` Andrew Lunn
2022-04-19 2:46 ` [PATCH v2 2/4] ARM: dts: dove: Update sdio-host " Chris Packham
2022-04-19 12:09 ` Andrew Lunn
2022-04-19 2:46 ` [PATCH v2 3/4] dt-bindings: mmc: convert orion-sdio to JSON schema Chris Packham
2022-04-19 12:10 ` Andrew Lunn
2022-04-21 13:54 ` Ulf Hansson
2022-04-19 2:46 ` [PATCH v2 4/4] dt-bindings: mmc: convert sdhci-dove " Chris Packham
2022-04-19 7:39 ` Krzysztof Kozlowski
2022-04-19 12:11 ` Andrew Lunn
2022-04-21 13:54 ` Ulf Hansson
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=20220419024611.1327525-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=adrian.hunter@intel.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=ulf.hansson@linaro.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).