All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@i3micro.com>
To: Sergei Shtylylov <sshtylyov@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] NAND: Fix NAND ECC errors on AMD Au1550
Date: Tue, 01 Nov 2005 16:50:39 +0100	[thread overview]
Message-ID: <1130860239.16267.62.camel@localhost> (raw)
In-Reply-To: <436789E3.6010706@ru.mvista.com>

On Tue, 2005-11-01 at 18:29 +0300, Sergei Shtylylov wrote:
> > Attached is an incremental patch on top of Sergeys latest patch
> > (yesterday). Is that's ok, or should I do the same for the old one?
> 
>     Alas, I have to NAK your patch.

Ok.

>     Note, that with NAND_CMD_READID page_addr of -1 is always passed (so we 
> only write out the 1-byte column address) on the address phase, and we just 
> won't get there for READID command....

>     Therefore, neither -CE wil be overridden nor local_irq_save() be executed 
> for READID case...

Well, I guess I cheated a bit.

In the more well-tested version of the driver (using your older patch),
I actually do the force-assert for (column != -1) as well.

When doing the merge here, I must have messed up something while testing
and out of pure confusion decided that I didn't have to include that
part.

> > +	if (ce_override) {
> >  		/* Apply a short delay always to ensure that we do wait tWB. */
> >  		ndelay(100);
> >  		/* Wait for a chip to become ready... */
> > @@ -442,6 +431,19 @@ static void au1550_command(struct mtd_in
> >  		local_irq_restore(flags);
> 
>     ... and later you get the CPU flags corrupted.

Oops...
See above.

>     Has your READID problem arisen with or without my patch?

Your patch fixed the problem of a collision with the NOR flash.
But only after I added the READID force-assert. Before that it caused
the NAND chip to stop being detected.

regards
	/
		Leif

  reply	other threads:[~2005-11-01 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 20:44 [PATCH] NAND: Fix NAND ECC errors on AMD Au1550 Sergei Shtylylov
2005-10-30  4:36 ` Pete Popov
2005-10-31  7:58 ` Pete Popov
2005-10-31 14:39   ` Leif Lindholm
2005-10-31 16:00     ` Pete Popov
2005-11-01 14:49       ` Leif Lindholm
2005-11-01 15:29         ` Sergei Shtylylov
2005-11-01 15:50           ` Leif Lindholm [this message]
2005-11-01 16:31             ` Sergei Shtylylov
2005-10-31 17:55     ` Sergei Shtylylov
2005-11-01  8:53 ` Pantelis Antoniou
2005-11-01 12:49   ` Sergei Shtylylov
2005-11-01 13:00     ` Pantelis Antoniou

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=1130860239.16267.62.camel@localhost \
    --to=leif.lindholm@i3micro.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sshtylyov@ru.mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.