linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Sudhakar Rajashekhara" <sudhakar.raj@ti.com>
To: "'Andrew Morton'" <akpm@linux-foundation.org>
Cc: linux-mtd@lists.infradead.org,
	davinci-linux-open-source@linux.davincidsp.com,
	nsnehaprabha@ti.com, dwmw2@infradead.org
Subject: RE: [PATCH] mtd-nand: davinci: correct 4-bit error correction
Date: Mon, 12 Jul 2010 11:58:18 +0530	[thread overview]
Message-ID: <00c701cb218b$6e4d6dd0$4ae84970$@raj@ti.com> (raw)
In-Reply-To: <20100709153932.0a6cdbcd.akpm@linux-foundation.org>

On Sat, Jul 10, 2010 at 04:09:32, Andrew Morton wrote:
> On Fri,  9 Jul 2010 10:59:49 +0530
> Sudhakar Rajashekhara <sudhakar.raj@ti.com> wrote:
> 
> > +
> > +	/*
> > +	 * ECC_STATE field reads 0x3 (Error correction complete) immediately
> > +	 * after setting the 4BITECC_ADD_CALC_START bit. So if you immediately
> > +	 * begin trying to poll for the state, you may fall right out of your
> > +	 * loop without any of the correction calculations having taken place.
> > +	 * The recommendation from the hardware team is to wait till ECC_STATE
> > +	 * reads less than 4, which means ECC HW has entered correction state.
> > +	 */
> > +	do {
> > +		ecc_state = (davinci_nand_readl(info,
> > +				NANDFSR_OFFSET) >> 8) & 0x0f;
> > +		cpu_relax();
> > +	} while ((ecc_state < 4) && time_before(jiffies, timeo));
> 
> An up-to-100-milliseond busy wait is pretty bad.  For how long do you
> expect this to spin in practice?

On the hardware, I have never seen this taking 100 msec to come out of
the loop. I'll check with the hardware folks on the maximum time to wait
for, before the ECC engine is ready.

Thanks,
Sudhakar

  reply	other threads:[~2010-07-12  6:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09  5:29 [PATCH] mtd-nand: davinci: correct 4-bit error correction Sudhakar Rajashekhara
2010-07-09 22:39 ` Andrew Morton
2010-07-12  6:28   ` Sudhakar Rajashekhara [this message]
2010-07-13  9:32     ` Sudhakar Rajashekhara
2010-07-13 17:41       ` Andrew Morton
2010-07-14 11:25         ` Sudhakar Rajashekhara
  -- strict thread matches above, loose matches on Subject: below --
2009-11-03 10:31 [PATCH] mtd-nand: davinci: Correct " Sudhakar Rajashekhara
2009-11-10 15:05 ` Artem Bityutskiy

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='00c701cb218b$6e4d6dd0$4ae84970$@raj@ti.com' \
    --to=sudhakar.raj@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nsnehaprabha@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).