From: Boris Brezillon <boris.brezillon@bootlin.com>
To: IKEGAMI Tokunori <ikegami@allied-telesis.co.jp>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
PACKHAM Chris <chris.packham@alliedtelesis.co.nz>
Subject: Re: mtd: cfi_cmdset_0002: Read data 3 times to check write operation status
Date: Wed, 9 May 2018 16:00:08 +0200 [thread overview]
Message-ID: <20180509160008.7079b73d@bbrezillon> (raw)
In-Reply-To: <TY1PR01MB09540E30A53D361D54CEA16EDC880@TY1PR01MB0954.jpnprd01.prod.outlook.com>
On Tue, 24 Apr 2018 05:54:43 +0000
IKEGAMI Tokunori <ikegami@allied-telesis.co.jp> wrote:
> Hi,
>
> Let us consult to change mtd cfi_cmdset_0002 to read data 3 times as below patch.
> Can we change the mtd cfi_cmdset_0002 driver like this?
> If any comment or concern please let us know.
>
> From d924822c996b9c0eccc815e5018a0c3ea6077137 Mon Sep 17 00:00:00 2001
> From: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
> Date: Tue, 24 Apr 2018 13:26:37 +0900
> Subject: [PATCH 2/2] mtd: cfi_cmdset_0002: Read data 3 times to check write
> operation status
>
> Cypress S29GLxxxP flash is needed to read data 3 times to check DQ6 toggles.
> Actually the read data is sometimes changed by the 3rd reading.
> Also this is caused on other flash device also.
> The flash write failure is possible to be caused by the error.
> To resolve the issue change the read number of times to 3 from 2.
Is this patch still needed, or is [1] supposed to replace it?
[1]http://patchwork.ozlabs.org/patch/910857/
next prev parent reply other threads:[~2018-05-09 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 5:54 mtd: cfi_cmdset_0002: Read data 3 times to check write operation status IKEGAMI Tokunori
2018-04-24 11:04 ` Joakim Tjernlund
2018-04-24 14:08 ` IKEGAMI Tokunori
2018-04-24 17:21 ` Joakim Tjernlund
2018-04-25 0:11 ` IKEGAMI Tokunori
2018-04-25 2:17 ` [PATCH] " smtpuser
2018-05-09 14:00 ` Boris Brezillon [this message]
2018-05-09 14:32 ` IKEGAMI Tokunori
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=20180509160008.7079b73d@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=ikegami@allied-telesis.co.jp \
--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