public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] spl: nand: simple: replace readb() with chip specific read_buf()
Date: Thu, 16 Jul 2015 10:02:31 +0200	[thread overview]
Message-ID: <20150716100231.677f8d16@lilith> (raw)
In-Reply-To: <1437003228-14746-2-git-send-email-vz@mleia.com>

Hello Vladimir,

On Thu, 16 Jul 2015 02:33:45 +0300, Vladimir Zapolskiy <vz@mleia.com>
wrote:
> Some NAND controllers define custom functions to read data out,
> respect this in order to correctly support bad block handling in
> simple SPL NAND framework.
> 
> NAND controller specific read_buf() is used even to read 1 byte in
> case of connected 8-bit NAND device, it turns out that read_byte()
> may become outdated.
> 
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
> ---
>  drivers/mtd/nand/nand_spl_simple.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/mtd/nand/nand_spl_simple.c b/drivers/mtd/nand/nand_spl_simple.c
> index 700ca32..e69f662 100644
> --- a/drivers/mtd/nand/nand_spl_simple.c
> +++ b/drivers/mtd/nand/nand_spl_simple.c
> @@ -115,6 +115,7 @@ static int nand_command(int block, int page, uint32_t offs,
>  static int nand_is_bad_block(int block)
>  {
>  	struct nand_chip *this = mtd.priv;
> +	u_char bb_data[2];
>  
>  	nand_command(block, 0, CONFIG_SYS_NAND_BAD_BLOCK_POS,
>  		NAND_CMD_READOOB);
> @@ -123,10 +124,12 @@ static int nand_is_bad_block(int block)
>  	 * Read one byte (or two if it's a 16 bit chip).
>  	 */
>  	if (this->options & NAND_BUSWIDTH_16) {
> -		if (readw(this->IO_ADDR_R) != 0xffff)
> +		this->read_buf(&mtd, bb_data, 2);
> +		if (bb_data[0] != 0xff || bb_data[1] != 0xff)
>  			return 1;
>  	} else {
> -		if (readb(this->IO_ADDR_R) != 0xff)
> +		this->read_buf(&mtd, bb_data, 1);
> +		if (bb_data[0] != 0xff)
>  			return 1;
>  	}
>  
> -- 
> 2.1.4
> 

The way you describe this patch, it looks like a bug that should have
bitten way more boards than lpc32xx. Did you have a look at some other
boards to see why this did not affect them? Conversively, what is the
actual failure scenario that led you to writing this patch? 

Amicalement,
-- 
Albert.

  reply	other threads:[~2015-07-16  8:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 23:33 [U-Boot] [PATCH 0/4] lpc32xx: devkit3250 board update Vladimir Zapolskiy
2015-07-15 23:33 ` [U-Boot] [PATCH 1/4] spl: nand: simple: replace readb() with chip specific read_buf() Vladimir Zapolskiy
2015-07-16  8:02   ` Albert ARIBAUD [this message]
2015-07-16 11:31     ` Vladimir Zapolskiy
2015-07-16 12:43       ` Albert ARIBAUD
2015-07-16 13:48         ` Vladimir Zapolskiy
2015-07-16 14:12           ` Albert ARIBAUD
2015-07-16 19:30             ` Scott Wood
2015-07-15 23:33 ` [U-Boot] [PATCH 2/4] nand: lpc32xx: add SLC NAND controller support Vladimir Zapolskiy
2015-07-16 12:53   ` Albert ARIBAUD
2015-07-16 20:14     ` Scott Wood
2015-07-16 20:18       ` Vladimir Zapolskiy
2015-07-16 20:20   ` Scott Wood
2015-07-16 20:29     ` Vladimir Zapolskiy
2015-07-15 23:33 ` [U-Boot] [PATCH 3/4] lpc32xx: devkit3250: update of board configuration Vladimir Zapolskiy
2015-07-16  7:27   ` Albert ARIBAUD
2015-07-16 12:05     ` Vladimir Zapolskiy
2015-07-16 12:45       ` Albert ARIBAUD
2015-07-15 23:33 ` [U-Boot] [PATCH 4/4] lpc32xx: devkit3250: add spl build support Vladimir Zapolskiy

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=20150716100231.677f8d16@lilith \
    --to=albert.u.boot@aribaud.net \
    --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