From: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
To: Liang Yang <liang.yang@amlogic.com>,
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>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: <oxffffaa@gmail.com>, <kernel@sberdevices.ru>,
Arseniy Krasnov <AVKrasnov@sberdevices.ru>,
<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [RFC PATCH v1 0/2] support 512B ECC step size for Meson NAND
Date: Wed, 28 Jun 2023 12:29:34 +0300 [thread overview]
Message-ID: <20230628092937.538683-1-AVKrasnov@sberdevices.ru> (raw)
Hello,
this patchset adds support for 512B ECC step size for Meson NAND. Current
implementation only supports 1024B. There are two patches:
1) Update for device tree bindings to replace 'const' type of field
'nand-ecc-step-size' with 'enum' which contains 512 and 1024. Example
is also updated.
2) Update for Meson driver - new enum value for 512B ECC and reworked
ECC capabilities structure to support both 512B and 1024B ECC. By
default this driver uses 1024B ECC, 512B could be enabled in device
tree.
Arseniy Krasnov (2):
dt-bindings: nand: meson: support for 512B ECC step size
mtd: rawnand: meson: support for 512B ECC step size
.../bindings/mtd/amlogic,meson-nand.yaml | 3 +-
drivers/mtd/nand/raw/meson_nand.c | 47 ++++++++++++++-----
2 files changed, 37 insertions(+), 13 deletions(-)
--
2.35.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2023-06-28 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:29 Arseniy Krasnov [this message]
2023-06-28 9:29 ` [RFC PATCH v1 1/2] dt-bindings: nand: meson: support for 512B ECC step size Arseniy Krasnov
2023-06-29 16:19 ` Rob Herring
2023-07-04 8:35 ` Miquel Raynal
2023-06-28 9:29 ` [RFC PATCH v1 2/2] mtd: rawnand: " Arseniy Krasnov
2023-07-04 8:36 ` Miquel Raynal
2023-07-04 9:23 ` Arseniy Krasnov
2023-07-04 9:41 ` Miquel Raynal
2023-07-04 9:46 ` Arseniy Krasnov
2023-07-04 9:56 ` Miquel Raynal
2023-07-04 10:21 ` Arseniy Krasnov
2023-07-04 13:41 ` Miquel Raynal
2023-07-04 15:07 ` Arseniy Krasnov
2023-07-04 15:32 ` Miquel Raynal
2023-07-04 17:07 ` Arseniy Krasnov
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=20230628092937.538683-1-AVKrasnov@sberdevices.ru \
--to=avkrasnov@sberdevices.ru \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=liang.yang@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=miquel.raynal@bootlin.com \
--cc=neil.armstrong@linaro.org \
--cc=oxffffaa@gmail.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
all inboxes | Powered by JetHome®