public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 256
Date: Mon, 13 Apr 2015 10:39:46 +0200	[thread overview]
Message-ID: <1428914386.26500.5.camel@embedded.rocks> (raw)
In-Reply-To: <1428826652-314-1-git-send-email-hs@denx.de>

Hi Heiko,

On So, 2015-04-12 at 10:17 +0200, Heiko Schocher wrote:
> On the i.mx6 based aristainetos2 board a Toshiba TH58NYG3S0HBAI4
> is used, which has 4096 pagesize and 256b oob. The ECC strength
> was not correct detected by U-Boot
> 
> Signed-off-by: Heiko Schocher <hs@denx.de>
> ---
> 
>  drivers/mtd/nand/mxs_nand.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/mtd/nand/mxs_nand.c 
> b/drivers/mtd/nand/mxs_nand.c
> index 2d2b938..00bf036 100644
> --- a/drivers/mtd/nand/mxs_nand.c
> +++ b/drivers/mtd/nand/mxs_nand.c
> @@ -163,6 +163,9 @@ static inline uint32_t 
> mxs_nand_get_ecc_strength(uint32_t page_data_size,
>  
>               if (page_oob_size == 224)
>                       return 16;
> +
> +             if (page_oob_size == 256)
> +                     return 18;
>       }
>  
>       return 0;

How about calculation the ECC strength dynamically? Peng Fan from 
Freescale send a patch doing this in December 2014 which was already 
reviewed by Marek:
https://patchwork.ozlabs.org/patch/422756/

It is also necessary to change the calculation in mxsboot...

Best regards
J?rg Krause

  reply	other threads:[~2015-04-13  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12  8:17 [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 256 Heiko Schocher
2015-04-13  8:39 ` Jörg Krause [this message]
2015-04-13  8:42   ` Marek Vasut
2015-04-13  9:01     ` Heiko Schocher
2015-04-13  9:12       ` Marek Vasut
2015-04-13 11:38       ` Jörg Krause
2015-04-13 13:25         ` Heiko Schocher

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=1428914386.26500.5.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=u-boot@lists.denx.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