From: Vadym Kochan <vadym.kochan@plvision.eu>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Roger Quadros <rogerq@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Liang Yang <liang.yang@amlogic.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Aviram Dali <aviramd@marvell.com>,
Vadym Kochan <vadym.kochan@plvision.eu>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Elad Nachman <enachman@marvell.com>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 0/3] mtd: rawnand: marvell: add support for AC5 SoC
Date: Wed, 19 Oct 2022 11:20:37 +0300 [thread overview]
Message-ID: <20221019082046.30160-1-vadym.kochan@plvision.eu> (raw)
This series adds support for AC5 SoC.
The following changes were made to add AC5 support:
1) Modify Marvell nand NFC timing set for mode 0
2) fix validation in AC5 Nand driver for ONFI timings values modes 1 and 3
3) remove unnecessary nand timing-mode in device tree of ac5.dtsi
4) add nand missing AC5X layouts , add option to use ndtr predefined values
5) Zero steps and total fields of ecc in ecc controller initialization so
nand_scan_tail() will calculate these two fields, otherwise
NAND initialization will fail with kernel 5.15 and above.
Aviram Dali (2):
dt-bindings: mtd: Add AC5 specific binding
mtd: rawnand: marvell: add support for AC5 SoC
Vadym Kochan (1):
mtd: rawnand: Partially revert 4114f97c41cd ("mtd: rawnand: Get rid of
a few unused definitions")
.../devicetree/bindings/mtd/marvell-nand.txt | 1 +
drivers/mtd/nand/raw/Kconfig | 2 +-
drivers/mtd/nand/raw/marvell_nand.c | 277 ++++++++++++++++--
drivers/mtd/nand/raw/nand_timings.c | 14 +
include/linux/mtd/rawnand.h | 3 +
5 files changed, 264 insertions(+), 33 deletions(-)
--
2.17.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2022-10-19 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:20 Vadym Kochan [this message]
2022-10-19 8:20 ` [PATCH 1/3] mtd: rawnand: Partially revert 4114f97c41cd ("mtd: rawnand: Get rid of a few unused definitions") Vadym Kochan
2022-10-19 8:20 ` [PATCH 2/3] dt-bindings: mtd: Add AC5 specific binding Vadym Kochan
2022-10-19 8:46 ` Miquel Raynal
2022-10-20 13:14 ` Vadym Kochan
2022-10-20 23:13 ` Chris Packham
2022-10-21 19:56 ` Vadym Kochan
2022-10-19 8:20 ` [PATCH 3/3] mtd: rawnand: marvell: add support for AC5 SoC Vadym Kochan
2022-10-19 8:45 ` Miquel Raynal
2023-05-25 0:53 ` [PATCH 0/3] " Chris Packham
2023-05-26 12:01 ` Vadym Kochan
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=20221019082046.30160-1-vadym.kochan@plvision.eu \
--to=vadym.kochan@plvision.eu \
--cc=aviramd@marvell.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=enachman@marvell.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=liang.yang@amlogic.com \
--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=rogerq@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=vigneshr@ti.com \
--cc=wsa+renesas@sang-engineering.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).