From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 0/3] mtd: fix AMD/Intel flash bugs
Date: Thu, 15 Mar 2018 16:54:54 +0100 [thread overview]
Message-ID: <20180315165454.5bf24ec0@bbrezillon> (raw)
In-Reply-To: <1520784361.4790.86.camel@infinera.com>
On Sun, 11 Mar 2018 16:06:03 +0000
Joakim Tjernlund <Joakim.Tjernlund@infinera.com> wrote:
> On Thu, 2018-03-01 at 14:39 +0100, Joakim Tjernlund wrote:
> > This fixes a bug which allows read/write to a erase block currently
> > erasing.
> > Also works around a chip bug in Micron 28F00AP30 chips.
> >
> > Joakim Tjernlund (3):
> > cfi_cmdset_0001: Do not allow read/write to suspend erase block.
> > cfi_cmdset_0001: Workaround Micron Erase suspend bug.
> > cfi_cmdset_0002: Do not allow read/write to suspend erase block.
> >
> > drivers/mtd/chips/cfi_cmdset_0001.c | 33 ++++++++++++++++++++++++++++-----
> > drivers/mtd/chips/cfi_cmdset_0002.c | 9 ++++++---
> > include/linux/mtd/flashchip.h | 1 +
> > 3 files changed, 35 insertions(+), 8 deletions(-)
> >
>
> Ping?
You didn't Cc the MTD maintainers, so that's not surprising you don't
get a reply from us :P.
> This is a fairly serious bug as it confuses the flash state machine,
> making further flash access fail.
I'll try to have a look.
>
> Jocke
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-15 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 13:39 [PATCH 0/3] mtd: fix AMD/Intel flash bugs Joakim Tjernlund
2018-03-01 13:39 ` [PATCH 1/3] cfi_cmdset_0001: Do not allow read/write to suspend erase block Joakim Tjernlund
2018-03-22 14:14 ` Richard Weinberger
2018-03-22 14:26 ` Joakim Tjernlund
2018-04-24 15:45 ` Boris Brezillon
2018-03-01 13:39 ` [PATCH 2/3] cfi_cmdset_0001: Workaround Micron Erase suspend bug Joakim Tjernlund
2018-03-20 23:06 ` Richard Weinberger
2018-03-21 0:02 ` Joakim Tjernlund
2018-03-01 13:39 ` [PATCH 3/3] cfi_cmdset_0002: Do not allow read/write to suspend erase block Joakim Tjernlund
2018-03-22 14:21 ` Richard Weinberger
2018-03-22 14:27 ` Joakim Tjernlund
2018-03-11 16:06 ` [PATCH 0/3] mtd: fix AMD/Intel flash bugs Joakim Tjernlund
2018-03-12 9:09 ` Andrea Adami
2018-03-12 11:11 ` Joakim Tjernlund
2018-03-15 15:54 ` Boris Brezillon [this message]
2018-03-15 17:55 ` Joakim Tjernlund
2018-03-15 18:02 ` Boris Brezillon
2018-04-04 20:27 ` Joakim Tjernlund
2018-04-20 19:05 ` Boris Brezillon
2018-04-21 12:47 ` Joakim Tjernlund
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=20180315165454.5bf24ec0@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Joakim.Tjernlund@infinera.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox