From: Gary Thomas <gary@mlbassoc.com>
To: Steffen Rumler <Steffen.Rumler@siemens.com>
Cc: linux-mtd@lists.infradead.org
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BUG in mtd/chips/cfi_cmdset_0002.c for 64bit width flashes (linuxppc_2_4_devel)
Date: Fri, 06 Feb 2004 07:03:49 -0700 [thread overview]
Message-ID: <1076076229.27984.182.camel@hermes> (raw)
In-Reply-To: <40239C69.5040803@siemens.com>
On Fri, 2004-02-06 at 06:53, Steffen Rumler wrote:
> Hi,
>
> We have found the following bug in mtd/chips/cfi_cmdset_0002.c
> for 64bit bus width.
>
> The routine do_write_oneword() uses the DQ6 algorithm in order
> to detect the end of programming phase (see bitkeeper: linuxppc_2_4_devel)
>
>
> oldstatus = cfi_read(map, adr);
> status = cfi_read(map, adr);
>
> while( (status & dq6) != (oldstatus & dq6) &&
> (status & dq5) != dq5 &&
> !time_after(jiffies, timeo) ) {
>
> if (need_resched()) {
> cfi_spin_unlock(chip->mutex);
> yield();
> cfi_spin_lock(chip->mutex);
> } else
> udelay(1);
>
> oldstatus = cfi_read( map, adr );
> status = cfi_read( map, adr );
> }
>
> There are two contiguous calls of cfi_read() to check for the DQ6 toggling.
>
> But for 64bit one cfi_read() results in two flash accesses, one for
> the upper 32bit and the other for lower 32bit. In this way the DQ6 bits toggle
> for the two accesses related to one cfi_read(). The first access will be
> compared with the third and the second with the fourth.
> The end detection is broken, the body of the while loop will never be executed.
>
> I suggest to switch to the alternative DQ7 algorithm.
You should probably discuss this with the folks that support the MTD
layer (cc'd)
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next parent reply other threads:[~2004-02-06 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40239C69.5040803@siemens.com>
2004-02-06 14:03 ` Gary Thomas [this message]
2004-02-06 19:55 ` BUG in mtd/chips/cfi_cmdset_0002.c for 64bit width flashes (linuxppc_2_4_devel) Eric W. Biederman
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=1076076229.27984.182.camel@hermes \
--to=gary@mlbassoc.com \
--cc=Steffen.Rumler@siemens.com \
--cc=linux-mtd@lists.infradead.org \
/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