From: Boris Brezillon <boris.brezillon@bootlin.com>
To: IKEGAMI Tokunori <ikegami@allied-telesis.co.jp>
Cc: Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
PACKHAM Chris <chris.packham@alliedtelesis.co.nz>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: cfi_cmdset_0002: Change erase functions to retry for error
Date: Tue, 8 May 2018 13:20:37 +0200 [thread overview]
Message-ID: <20180508132037.152cc581@bbrezillon> (raw)
In-Reply-To: <TY1PR01MB0954474CBDBF98D0E3D3E648DC9A0@TY1PR01MB0954.jpnprd01.prod.outlook.com>
Hello,
On Tue, 8 May 2018 10:20:29 +0000
IKEGAMI Tokunori <ikegami@allied-telesis.co.jp> wrote:
> From: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
>
> For the word write functions it is retried for error.
> But it is not implemented to retry for the erase functions.
> To make sure for the erase functions change to retry as same.
Can you give a bit more context, like why this is needed, where did
you see the problem (which chip/controller), ...
>
> Signed-off-by: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
> Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Boris Brezillon <boris.brezillon@free-electrons.com>
> Cc: Marek Vasut <marek.vasut@gmail.com>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
> Cc: linux-mtd@lists.infradead.org
> ---
> drivers/mtd/chips/cfi_cmdset_0002.c | 36 +++++++++++++++++++++++-------------
> 1 file changed, 23 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
> index 56aa6b75213d..e2dc020cd102 100644
> --- a/drivers/mtd/chips/cfi_cmdset_0002.c
> +++ b/drivers/mtd/chips/cfi_cmdset_0002.c
> @@ -42,7 +42,7 @@
> #define AMD_BOOTLOC_BUG
> #define FORCE_WORD_WRITE 0
>
> -#define MAX_WORD_RETRIES 3
> +#define MAX_WRITE_RETRIES 3
Not sure why you rename this macro, but if it's needed can you do that
in a separate patch?
>
> #define SST49LF004B 0x0060
> #define SST49LF040B 0x0050
> @@ -207,7 +207,7 @@ static void fixup_use_write_buffers(struct mtd_info *mtd)
> struct map_info *map = mtd->priv;
> struct cfi_private *cfi = map->fldrv_priv;
> if (cfi->cfiq->BufWriteTimeoutTyp) {
> - pr_debug("Using buffer write method\n" );
> + pr_debug("Using buffer write method\n");
Same for coding style issues, they should be fixed in a separate commit.
> mtd->_write = cfi_amdstd_write_buffers;
> }
> }
> @@ -1577,7 +1577,7 @@ static int __xipram do_write_oneword(struct map_info *map, struct flchip *chip,
> }
>
> pr_debug("MTD %s(): WRITE 0x%.8lx(0x%.8lx)\n",
> - __func__, adr, datum.x[0] );
> + __func__, adr, datum.x[0]);
>
> if (mode == FL_OTP_WRITE)
> otp_enter(map, chip, adr, map_bankwidth(map));
> @@ -1643,10 +1643,10 @@ static int __xipram do_write_oneword(struct map_info *map, struct flchip *chip,
> /* Did we succeed? */
> if (!chip_good(map, adr, datum)) {
> /* reset on all failures. */
> - map_write( map, CMD(0xF0), chip->start );
> + map_write(map, CMD(0xF0), chip->start);
> /* FIXME - should have reset delay before continuing */
>
> - if (++retry_cnt <= MAX_WORD_RETRIES)
> + if (++retry_cnt <= MAX_WRITE_RETRIES)
> goto retry;
>
> ret = -EIO;
> @@ -1821,7 +1821,7 @@ static int __xipram do_write_buffer(struct map_info *map, struct flchip *chip,
> datum = map_word_load(map, buf);
>
> pr_debug("MTD %s(): WRITE 0x%.8lx(0x%.8lx)\n",
> - __func__, adr, datum.x[0] );
> + __func__, adr, datum.x[0]);
>
> XIP_INVAL_CACHED_RANGE(map, adr, len);
> ENABLE_VPP(map);
> @@ -2105,7 +2105,7 @@ static int do_panic_write_oneword(struct map_info *map, struct flchip *chip,
> map_write(map, CMD(0xF0), chip->start);
> /* FIXME - should have reset delay before continuing */
>
> - if (++retry_cnt <= MAX_WORD_RETRIES)
> + if (++retry_cnt <= MAX_WRITE_RETRIES)
> goto retry;
>
> ret = -EIO;
> @@ -2240,6 +2240,7 @@ static int __xipram do_erase_chip(struct map_info *map, struct flchip *chip)
> unsigned long int adr;
> DECLARE_WAITQUEUE(wait, current);
> int ret = 0;
> + int retry_cnt = 0;
>
> adr = cfi->addr_unlock1;
>
> @@ -2251,12 +2252,13 @@ static int __xipram do_erase_chip(struct map_info *map, struct flchip *chip)
> }
>
> pr_debug("MTD %s(): ERASE 0x%.8lx\n",
> - __func__, chip->start );
> + __func__, chip->start);
>
> XIP_INVAL_CACHED_RANGE(map, adr, map->size);
> ENABLE_VPP(map);
> xip_disable(map, chip, adr);
>
> + retry:
> cfi_send_gen_cmd(0xAA, cfi->addr_unlock1, chip->start, map, cfi, cfi->device_type, NULL);
> cfi_send_gen_cmd(0x55, cfi->addr_unlock2, chip->start, map, cfi, cfi->device_type, NULL);
> cfi_send_gen_cmd(0x80, cfi->addr_unlock1, chip->start, map, cfi, cfi->device_type, NULL);
> @@ -2297,7 +2299,7 @@ static int __xipram do_erase_chip(struct map_info *map, struct flchip *chip)
>
> if (time_after(jiffies, timeo)) {
> printk(KERN_WARNING "MTD %s(): software timeout\n",
> - __func__ );
> + __func__);
> break;
> }
>
> @@ -2307,9 +2309,12 @@ static int __xipram do_erase_chip(struct map_info *map, struct flchip *chip)
> /* Did we succeed? */
> if (!chip_good(map, adr, map_word_ff(map))) {
> /* reset on all failures. */
> - map_write( map, CMD(0xF0), chip->start );
> + map_write(map, CMD(0xF0), chip->start);
> /* FIXME - should have reset delay before continuing */
>
> + if (++retry_cnt <= MAX_WRITE_RETRIES)
> + goto retry;
Shouldn't we have a MAX_ERASE_RETRY for that? Also, what makes you
think the following erase operations will work?
Thanks,
Boris
next prev parent reply other threads:[~2018-05-08 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 10:20 [PATCH] mtd: cfi_cmdset_0002: Change erase functions to retry for error IKEGAMI Tokunori
2018-05-08 11:20 ` Boris Brezillon [this message]
2018-05-08 14:15 ` IKEGAMI Tokunori
2018-05-08 16:52 ` IKEGAMI Tokunori
2018-05-08 17:11 ` Boris Brezillon
2018-05-08 17:35 ` IKEGAMI Tokunori
2018-05-08 18:02 ` Boris Brezillon
2018-05-09 0:27 ` IKEGAMI Tokunori
2018-05-09 8:18 ` Joakim Tjernlund
2018-05-09 10:20 ` IKEGAMI Tokunori
2018-05-09 10:26 ` IKEGAMI Tokunori
2018-05-09 11:45 ` Boris Brezillon
2018-05-09 13:15 ` 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=20180508132037.152cc581@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=ikegami@allied-telesis.co.jp \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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