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, gregory.clement@bootlin.com
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v3 0/3] mtd: rawnand: marvell: add support for AC5 SoC
Date: Mon, 3 Jul 2023 15:50:41 +1200 [thread overview]
Message-ID: <20230703035044.2063303-1-chris.packham@alliedtelesis.co.nz> (raw)
This series adds support for the NAND Flash Controller on the AC5/AC5X SOC. Its
dependent series are all in mainline now so this should apply cleanly on top of
that.
I've tried to stick to the minimal changes required to get the NFC working on
the board I have (AC5X + S34ML02G2). Marvell's SDK has hard coded tables of
ndtr values for the different timing modes but so far that seems unnecessary.
Chris Packham (3):
dt-bindings: mtd: Add AC5 specific binding
arm64: dts: marvell: Add NAND flash controller to AC5
mtd: rawnand: marvell: add support for AC5 SoC
.../bindings/mtd/marvell,nand-controller.yaml | 1 +
arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi | 16 ++++++++++++++++
drivers/mtd/nand/raw/Kconfig | 2 +-
drivers/mtd/nand/raw/marvell_nand.c | 16 ++++++++++++++++
4 files changed, 34 insertions(+), 1 deletion(-)
--
2.41.0
next reply other threads:[~2023-07-03 3:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 3:50 Chris Packham [this message]
2023-07-03 3:50 ` [PATCH v3 1/3] dt-bindings: mtd: Add AC5 specific binding Chris Packham
2023-07-12 12:32 ` Miquel Raynal
2023-07-12 18:13 ` Conor Dooley
2023-07-13 7:23 ` Miquel Raynal
2023-07-12 20:36 ` Chris Packham
2023-07-13 7:57 ` Miquel Raynal
2023-07-03 3:50 ` [PATCH v3 2/3] arm64: dts: marvell: Add NAND flash controller to AC5 Chris Packham
2023-07-13 8:59 ` Gregory CLEMENT
2023-07-03 3:50 ` [PATCH v3 3/3] mtd: rawnand: marvell: add support for AC5 SoC Chris Packham
2023-07-13 7:57 ` Miquel Raynal
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=20230703035044.2063303-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.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=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).