public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Blackfin: nand: drain the write buffer before returning
Date: Fri, 7 May 2010 14:48:17 -0400	[thread overview]
Message-ID: <201005071448.19238.vapier@gentoo.org> (raw)
In-Reply-To: <20100507175151.GA26420@schlenkerla.am.freescale.net>

On Friday 07 May 2010 13:51:51 Scott Wood wrote:
> On Fri, May 07, 2010 at 01:25:48AM -0400, Mike Frysinger wrote:
> > From: Andrew Caldwell <Andrew.Caldwell@analog.com>
> > 
> > The current Blackfin nand write function fills up the write buffer but
> > returns before it has had a chance to drain.  On faster systems, this
> > isn't a problem as the operation finishes before the ECC registers are
> > read, but on slower systems the ECC may be incomplete when the core tries
> > to read it.
> > 
> > So wait for the buffer to drain once we're doing writing to it.
> > 
> > Signed-off-by: Andrew Caldwell <Andrew.Caldwell@analog.com>
> > Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> > ---
> > 
> >  drivers/mtd/nand/bfin_nand.c |    7 ++++++-
> >  1 files changed, 6 insertions(+), 1 deletions(-)
> 
> Applied to u-boot-nand-flash.

sorry, please drop this.  Andrew pointed out that i committed/posted the wrong 
version.  i'll send an update shortly.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100507/c651a82d/attachment.pgp 

  reply	other threads:[~2010-05-07 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  5:25 [U-Boot] [PATCH] Blackfin: nand: drain the write buffer before returning Mike Frysinger
2010-05-07 17:51 ` Scott Wood
2010-05-07 18:48   ` Mike Frysinger [this message]
2010-05-07 18:54     ` Scott Wood
2010-05-07 19:10 ` [U-Boot] [PATCH v2] " Mike Frysinger
2010-05-20 21:31   ` Scott Wood

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=201005071448.19238.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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