From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Huang Shijie <b32955@freescale.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: question: Why the nand_wait() wait for 20ms for nand program.
Date: Fri, 18 Jan 2013 13:26:13 +0100 [thread overview]
Message-ID: <50F93F65.90805@parrot.com> (raw)
In-Reply-To: <50F9023D.5040408@freescale.com>
Huang Shijie a écrit :
> Hi all:
> Why the nand_wait() wait for 20ms for nand program. could we
> expand this time to 40ms? I have a nand chip : Micron MT29F64G08CBABAWP.
> The chip's BUSY/READY pin may needs more then 20ms to become ready,
> though its
> datasheet tells me the tPROG's max value is 2.5ms.
>
Don't you have an hardware problem (missing pullup/down on ready busy pin) ?
If the datasheet say the max value is 2.5 ms , how it can be more than 20 ms.
Matthieu
next prev parent reply other threads:[~2013-01-18 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 8:05 question: Why the nand_wait() wait for 20ms for nand program Huang Shijie
2013-01-18 12:26 ` Matthieu CASTET [this message]
2013-01-21 3:34 ` Huang Shijie
2013-01-21 8:57 ` Matthieu CASTET
[not found] ` <50FD0554.8030108@freescale.com>
2013-01-21 9:15 ` Matthieu CASTET
2013-01-21 9:25 ` Huang Shijie
2013-01-21 9:32 ` Matthieu CASTET
2013-01-21 9:35 ` Huang Shijie
[not found] ` <50FF9068.1030709@freescale.com>
2013-02-01 16:58 ` question about mtd_torturetest.c Artem Bityutskiy
2013-02-04 5:19 ` Gupta, Pekon
2013-02-04 6:58 ` Artem Bityutskiy
2013-02-04 7:32 ` Huang Shijie
2013-01-22 2:46 ` question: Why the nand_wait() wait for 20ms for nand program Huang Shijie
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=50F93F65.90805@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.