From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, enachman@marvell.com,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v7 0/4] dt-bindings: mtd: marvell-nand: Add YAML scheme
Date: Wed, 31 May 2023 11:54:52 +1200 [thread overview]
Message-ID: <20230530235456.1009082-1-chris.packham@alliedtelesis.co.nz> (raw)
Add YAML scheme for the Marvell's NAND controller
to validate it's DT bindings. Old txt file is deleted,
not included the compatibles and properties which were marked as
deprecated.
Also fix node name in cp11x DTSI acording to nand-controller.yaml
I've picked up this series to hopefully get it over the line. I think I've
addressed all the feedback from the last round of review.
As of v7 I've re-ordered the patches so the fixups for the device trees come
before the schema so if the series is applied in order the various checkers
should pass cleanly.
Chris Packham (2):
ARM: dts: mvebu: align MTD partition nodes to dtschema
dt-bindings: mtd: marvell-nand: Remove deprecated compatibles
Vadym Kochan (2):
arm64: dts: marvell: cp11x: Fix nand_controller node name according to
YAML
dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme
.../bindings/mtd/marvell,nand-controller.yaml | 218 ++++++++++++++++++
.../devicetree/bindings/mtd/marvell-nand.txt | 126 ----------
MAINTAINERS | 1 -
arch/arm/boot/dts/armada-385-atl-x530.dts | 14 +-
arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 2 +-
5 files changed, 226 insertions(+), 135 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/marvell,nand-controller.yaml
delete mode 100644 Documentation/devicetree/bindings/mtd/marvell-nand.txt
--
2.40.1
next reply other threads:[~2023-05-30 23:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 23:54 Chris Packham [this message]
2023-05-30 23:54 ` [PATCH v7 1/4] arm64: dts: marvell: cp11x: Fix nand_controller node name according to YAML Chris Packham
2023-05-31 7:35 ` Miquel Raynal
2023-05-30 23:54 ` [PATCH v7 2/4] ARM: dts: mvebu: align MTD partition nodes to dtschema Chris Packham
2023-05-31 7:35 ` Miquel Raynal
2023-05-30 23:54 ` [PATCH v7 3/4] dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme Chris Packham
2023-05-31 12:35 ` Conor Dooley
2023-05-31 22:52 ` Chris Packham
2023-05-31 22:43 ` Chris Packham
2023-06-01 7:40 ` Miquel Raynal
2023-05-30 23:54 ` [PATCH v7 4/4] dt-bindings: mtd: marvell-nand: Remove deprecated compatibles Chris Packham
2023-05-31 7:33 ` Miquel Raynal
2023-05-31 22:36 ` Chris Packham
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=20230530235456.1009082-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=enachman@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--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).