From: <grmoore@altera.com>
To: <ggrahammoore@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marex@denx.de>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Sourav Poddar <sourav.poddar@ti.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
Jingoo Han <jg1.han@samsung.com>,
Insop Song <insop.song@gainspeed.com>,
Graham Moore <grmoore@altera.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
Alan Tull <atull@altera.com>, Dinh Nguyen <dinguyen@altera.com>,
Yves Vandervennet <rocket.yvanderv@gmail.com>
Subject: [PATCH] Add support for flag status register on Micron chips
Date: Tue, 8 Apr 2014 11:12:49 -0500 [thread overview]
Message-ID: <1396973570-13995-1-git-send-email-grmoore@altera.com> (raw)
From: Graham Moore <grmoore@altera.com>
This is a slightly different version of the patch that Insop Song
submitted (http://marc.info/?i=201403012022.10111.marex%20()%20denx%20!%20de).
I talked to Insop, and he agreed I should submit this patch as a follow-on to his.
This patch uses a flag in the m25p_ids[] array to determine which chips need
to use the FSR (Flag Status Register).
Rationale for using the FSR:
The Micron data sheets say we have to do this, at least for the multi-die 512M
and 1G parts (n25q512 and n25q00). In practice, if we don't check the FSR
for program/erase status, and we rely solely on the status register (SR),
then we get corrupted data in the flash.
Micron told us (Altera) that for multi-die chips based on the 65nm 256MB
die, we need to check the SR first, then check the FSR, which is why the
wait_for_fsr_ready function does that. Future chips based on 45 nm 512MB die
will use the FSR only.
Thanks.
Graham Moore (1):
Add support for flag status register on Micron chips.
drivers/mtd/devices/m25p80.c | 94 +++++++++++++++++++++++++++++++++++-------
1 file changed, 80 insertions(+), 14 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-04-08 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 16:12 grmoore [this message]
2014-04-08 16:12 ` grmoore
2014-04-08 16:52 ` Insop Song
2014-04-09 10:06 ` Marek Vasut
2014-04-09 10:16 ` Jingoo Han
2014-04-09 10:21 ` Jingoo Han
2014-04-09 10:03 ` Marek Vasut
2014-04-09 11:09 ` Gerhard Sittig
2014-04-09 18:14 ` Graham Moore
2014-04-09 18:31 ` Marek Vasut
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=1396973570-13995-1-git-send-email-grmoore@altera.com \
--to=grmoore@altera.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=atull@altera.com \
--cc=computersforpeace@gmail.com \
--cc=dinguyen@altera.com \
--cc=dwmw2@infradead.org \
--cc=geert+renesas@linux-m68k.org \
--cc=ggrahammoore@gmail.com \
--cc=insop.song@gainspeed.com \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=rocket.yvanderv@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sourav.poddar@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
Powered by JetHome