From: Artem Bityutskiy <dedekind@infradead.org>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND: Verify probe by retrying to checking the results match
Date: Mon, 14 Apr 2008 16:33:47 +0300 [thread overview]
Message-ID: <1208180027.5965.212.camel@sauron> (raw)
In-Reply-To: <20080414131603.950238663@fluff.org.uk>
On Mon, 2008-04-14 at 14:16 +0100, Ben Dooks wrote:
> 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>
Could you please put the same comment to the code, to make it easier for
the curious code reader understand why is the second read?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-04-14 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 13:16 NAND: Verify probe by retrying to checking the results match Ben Dooks
2008-04-14 13:33 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 13:58 Ben Dooks
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=1208180027.5965.212.camel@sauron \
--to=dedekind@infradead.org \
--cc=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