From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: pxa3xx: make ECC configuration checks more explicit
Date: Sun, 17 Nov 2013 01:57:05 -0300 [thread overview]
Message-ID: <20131117045704.GA17731@localhost> (raw)
In-Reply-To: <1384471108-28188-1-git-send-email-computersforpeace@gmail.com>
On Thu, Nov 14, 2013 at 03:18:28PM -0800, Brian Norris wrote:
> The Armada BCH configuration in this driver uses one of the two
> following ECC schemes:
>
> 16-bit correction per 2048 bytes
> 16-bit correction per 1024 bytes
>
> These are sufficient for mapping to the 4-bit per 512-bytes and 8-bit
> per 512-bytes (respectively) minimum correctability requirements of many
> common NAND.
>
> The current code only checks for the required strength (4-bit or 8-bit)
> without checking the ECC step size that is associated with that strength
> (and simply assumes it is 512). While that is often a safe assumption to
> make, let's make it explicit, since we have that information.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Acked-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> ---
> drivers/mtd/nand/pxa3xx_nand.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
> index cec81f0..3d143fe 100644
> --- a/drivers/mtd/nand/pxa3xx_nand.c
> +++ b/drivers/mtd/nand/pxa3xx_nand.c
> @@ -1364,9 +1364,13 @@ static int pxa_ecc_init(struct pxa3xx_nand_info *info,
>
> static int armada370_ecc_init(struct pxa3xx_nand_info *info,
> struct nand_ecc_ctrl *ecc,
> - int strength, int page_size)
> + int strength, int ecc_stepsize, int page_size)
> {
> - if (strength == 4 && page_size == 4096) {
> + /*
> + * Required ECC: 4-bit correction per 512 bytes
> + * Select: 16-bit correction per 2048 bytes
> + */
> + if (strength == 4 && ecc_stepsize == 512 && page_size == 4096) {
> info->ecc_bch = 1;
> info->chunk_size = 2048;
> info->spare_size = 32;
> @@ -1377,7 +1381,11 @@ static int armada370_ecc_init(struct pxa3xx_nand_info *info,
> ecc->strength = 16;
> return 1;
>
> - } else if (strength == 8 && page_size == 4096) {
> + /*
> + * Required ECC: 8-bit correction per 512 bytes
> + * Select: 16-bit correction per 1024 bytes
> + */
> + } else if (strength == 8 && ecc_stepsize == 512 && page_size == 4096) {
> info->ecc_bch = 1;
> info->chunk_size = 1024;
> info->spare_size = 0;
> @@ -1485,6 +1493,7 @@ KEEP_CONFIG:
> if (info->variant == PXA3XX_NAND_VARIANT_ARMADA370)
> ret = armada370_ecc_init(info, &chip->ecc,
> chip->ecc_strength_ds,
> + chip->ecc_step_ds,
> mtd->writesize);
> else
> ret = pxa_ecc_init(info, &chip->ecc,
> --
> 1.8.4.2
>
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-17 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 23:18 [PATCH] mtd: nand: pxa3xx: make ECC configuration checks more explicit Brian Norris
2013-11-17 4:57 ` Ezequiel Garcia [this message]
2013-11-18 17:33 ` Brian Norris
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=20131117045704.GA17731@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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