From: Ben Dooks <ben-linux@fluff.org>
To: linux-mtd@lists.infradead.org
Cc: Ben Dooks <ben-linux@fluff.org>
Subject: NAND: Verify probe by retrying to checking the results match
Date: Mon, 14 Apr 2008 14:58:58 +0100 [thread overview]
Message-ID: <20080414135858.404403374@fluff.org.uk> (raw)
[-- Attachment #1: simtec/simtec-drivers-mtd-nand-doubleprobe.patch --]
[-- Type: text/plain, Size: 1839 bytes --]
With modern systems using bus-hold instead of bus pull-up, it can
often lead to erroneous reporting of NAND devices where there are
none. Do a double probe to ensure that the result we got the first
time is repeatable, and if it is not then return that there is no
chip there.
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Index: linux-2.6.24-quilt17/drivers/mtd/nand/nand_base.c
===================================================================
--- linux-2.6.24-quilt17.orig/drivers/mtd/nand/nand_base.c 2008-03-18 10:07:07.000000000 +0000
+++ linux-2.6.24-quilt17/drivers/mtd/nand/nand_base.c 2008-04-14 14:49:06.000000000 +0100
@@ -2229,6 +2229,7 @@ static struct nand_flash_dev *nand_get_f
{
struct nand_flash_dev *type = NULL;
int i, dev_id, maf_idx;
+ int tmp_id, tmp_manf;
/* Select the device */
chip->select_chip(mtd, 0);
@@ -2239,6 +2240,26 @@ static struct nand_flash_dev *nand_get_f
/* Read manufacturer and device IDs */
*maf_id = chip->read_byte(mtd);
dev_id = chip->read_byte(mtd);
+
+ /* Try again to make sure, as some systems the bus-hold or other
+ * interface concerns can cause random data which looks like a
+ * possibly credible NAND flash to appear. If the two results do
+ * not match, ignore the device completely.
+ */
+
+ chip->cmdfunc(mtd, NAND_CMD_READID, 0x00, -1);
+
+ /* Read manufacturer and device IDs */
+
+ tmp_manf = chip->read_byte(mtd);
+ tmp_id = chip->read_byte(mtd);
+
+ if (tmp_manf != *maf_id || tmp_id != dev_id) {
+ printk(KERN_INFO "%s: second ID read did not match "
+ "%02x,%02x against %02x,%02x\n", __func__,
+ *maf_id, dev_id, tmp_manf, tmp_id);
+ return ERR_PTR(-ENODEV);
+ }
/* Lookup the flash id */
for (i = 0; nand_flash_ids[i].name != NULL; i++) {
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next reply other threads:[~2008-04-14 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 13:58 Ben Dooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 13:16 NAND: Verify probe by retrying to checking the results match Ben Dooks
2008-04-14 13:33 ` 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=20080414135858.404403374@fluff.org.uk \
--to=ben-linux@fluff.org \
--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