public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org, Han Xu <han.xu@nxp.com>
Subject: Re: [PATCH] mtd: nand: gpmi: Fix ecc strength calculation
Date: Tue, 21 Jun 2016 16:46:39 +0200	[thread overview]
Message-ID: <20160621164639.23fde5d6@bbrezillon> (raw)
In-Reply-To: <1466519749-7729-1-git-send-email-s.hauer@pengutronix.de>

On Tue, 21 Jun 2016 16:35:49 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:

> BCH ECC correction works in chunks of 512 bytes, so a 2k page size nand
> is divided into 4 chunks. Hardware requires that each chunk has a full
> number of bytes, so when we need 9 bits per chunk we must round up to
> two bytes. The current code misses that and calculates a ECC strength
> of 18 for a 2048+128 byte page size NAND. ECC strength of 18 requires
> 30 bytes per chunk, so a total of 4 * (512 + 30) + 10 = 2178 bytes when
> the device only has a page size of 2176 bytes.

AFAIR, the GPMI/ECC engine operates at the bit level (which is a pain
to deal with BTW), and is only requiring a byte alignment on the total
number of ECC bits. So here, DIV_ROUND_UP(18 * 13 * 4, 8) = 117, which
fits in the 118 bytes (128 bytes - 10 bytes of 'metadata').

Han, can you confirm that?

> 
> Fix this by first calculating the number of bytes per chunk we have
> available for ECC which also makes it easier to follow the calculation.
> 
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 28 ++++++++--------------------
>  1 file changed, 8 insertions(+), 20 deletions(-)
> 
> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> index 6e46156..95fb3dc 100644
> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> @@ -119,32 +119,20 @@ static irqreturn_t bch_irq(int irq, void *cookie)
>  	return IRQ_HANDLED;
>  }
>  
> -/*
> - *  Calculate the ECC strength by hand:
> - *	E : The ECC strength.
> - *	G : the length of Galois Field.
> - *	N : The chunk count of per page.
> - *	O : the oobsize of the NAND chip.
> - *	M : the metasize of per page.
> - *
> - *	The formula is :
> - *		E * G * N
> - *	      ------------ <= (O - M)
> - *                  8
> - *
> - *      So, we get E by:
> - *                    (O - M) * 8
> - *              E <= -------------
> - *                       G * N
> - */
>  static inline int get_ecc_strength(struct gpmi_nand_data *this)
>  {
>  	struct bch_geometry *geo = &this->bch_geometry;
>  	struct mtd_info	*mtd = nand_to_mtd(&this->nand);
>  	int ecc_strength;
> +	int n;
> +
> +	/* number of ecc bytes we have per chunk */
> +	n = (mtd->oobsize - geo->metadata_size) / geo->ecc_chunk_count;
> +
> +	/* in bits */
> +	n <<= 3;
>  
> -	ecc_strength = ((mtd->oobsize - geo->metadata_size) * 8)
> -			/ (geo->gf_len * geo->ecc_chunk_count);
> +	ecc_strength = n / geo->gf_len;
>  
>  	/* We need the minor even number. */
>  	return round_down(ecc_strength, 2);

  reply	other threads:[~2016-06-21 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 14:35 [PATCH] mtd: nand: gpmi: Fix ecc strength calculation Sascha Hauer
2016-06-21 14:46 ` Boris Brezillon [this message]
2016-06-21 15:52   ` Han Xu
2016-06-22  6:33     ` Sascha Hauer
2016-06-22  8:34       ` Boris Brezillon

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=20160621164639.23fde5d6@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=han.xu@nxp.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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