From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
Cc: Liang Yang <liang.yang@amlogic.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>,
<oxffffaa@gmail.com>, <kernel@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: Re: [RFC PATCH v3 0/3] support 512B ECC step size for Meson NAND
Date: Sat, 15 Jul 2023 18:15:53 +0200 [thread overview]
Message-ID: <20230715181553.1d2b5637@xps-13> (raw)
In-Reply-To: <20230711122129.2635558-1-AVKrasnov@sberdevices.ru>
Hi Arseniy,
AVKrasnov@sberdevices.ru wrote on Tue, 11 Jul 2023 15:21:26 +0300:
> Hello,
>
> this patchset adds support for 512B ECC step size for Meson NAND. Current
> implementation only supports 1024B. There are three patches:
>
> 1) Update for device tree bindings to replace 'const' type of field
> 'nand-ecc-step-size' with 'enum' which contains 512 and 1024.
>
> 2) Update for device tree bindings to add dependency between properties
> 'nand-ecc-strength' and 'nand-ecc-step-size'.
>
> 3) 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.
This series does not apply correctly on nand/next, would you mind
rebasing (nand/next on linux-mtd) and sending it again?
BTW the "rfc" prefix is only needed for the "first" submission, when
you try something "new", otherwise it is no longer required.
Thanks,
Miquèl
next prev parent reply other threads:[~2023-07-15 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 12:21 [RFC PATCH v3 0/3] support 512B ECC step size for Meson NAND Arseniy Krasnov
2023-07-11 12:21 ` [RFC PATCH v3 1/3] dt-bindings: nand: meson: support for 512B ECC step size Arseniy Krasnov
2023-07-15 16:19 ` Miquel Raynal
2023-07-11 12:21 ` [RFC PATCH v3 2/3] dt-bindings: nand: meson: make ECC properties dependent Arseniy Krasnov
2023-07-14 15:55 ` Rob Herring
2023-07-14 19:22 ` Arseniy Krasnov
2023-07-14 20:44 ` Rob Herring
2023-07-11 12:21 ` [RFC PATCH v3 3/3] mtd: rawnand: meson: support for 512B ECC step size Arseniy Krasnov
2023-07-15 16:15 ` Miquel Raynal [this message]
2023-07-15 17:48 ` [RFC PATCH v3 0/3] support 512B ECC step size for Meson NAND Arseniy Krasnov
2023-07-16 13:24 ` 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=20230715181553.1d2b5637@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).