From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bastian Hecht <hechtb@googlemail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] mtd: nand: Add a STATUS CMD after write verification
Date: Fri, 27 Apr 2012 08:54:47 +0300 [thread overview]
Message-ID: <1335506087.1767.4.camel@koala> (raw)
In-Reply-To: <CABYn4sxYynuD3WN_9+fmieMfjjGeG+P3EAY+HoXmFtgn8x0PiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Wed, 2012-04-18 at 12:25 +0200, Bastian Hecht wrote:
> 2012/4/18 Bastian Hecht <hechtb@googlemail.com>:
> > When using CONFIG_MTD_NAND_VERIFY_WRITE=y an extra read command is sent
> > to the NAND chip after writing a page. We need an extra status command
> > to avoid hick-ups that lead to page write failures.
> > ---
> >
> > Hello all,
> >
> > I'm experiencing problems with my current setup and
> > CONFIG_MTD_NAND_VERIFY_WRITE=y. Usually the command sequence is like
> > 0x70 Status read
> > 0x80 0x10 Page prog
> > 0x70
> > 0x80 0x10 Page prog
> > 0x70
> > ...
> >
> > When activating write verification there is a read command before the
> > page prog.
>
> I've written this unclearly. I mean if we issue multiple page writes,
> the page writes are not preceeded by a status read, but by a page read
> command from the last verification.
Looks good to me. Could you send the final patch with final commit
message. Probably a small comment in the code is also a good idea.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-27 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 10:20 [RFC] mtd: nand: Add a STATUS CMD after write verification Bastian Hecht
2012-04-18 10:25 ` Bastian Hecht
2012-04-27 5:54 ` Artem Bityutskiy [this message]
2012-04-27 10:17 ` Bastian Hecht
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=1335506087.1767.4.camel@koala \
--to=dedekind1@gmail.com \
--cc=hechtb@googlemail.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 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.