From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "richard.weinberger@gmail.com" <richard.weinberger@gmail.com>
Cc: "boris.brezillon@free-electrons.com"
<boris.brezillon@free-electrons.com>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"joakim.tjernlund@transmode.se" <joakim.tjernlund@transmode.se>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>
Subject: Re: [PATCH 2/3] cfi_cmdset_0001: Workaround Micron Erase suspend bug.
Date: Wed, 21 Mar 2018 00:02:56 +0000 [thread overview]
Message-ID: <1521590574.4790.268.camel@infinera.com> (raw)
In-Reply-To: <CAFLxGvx9ZC6P9iYtODnvGi=qnE1Z9zNtdbo6fRAFBSpdsLzV8g@mail.gmail.com>
On Wed, 2018-03-21 at 00:06 +0100, Richard Weinberger wrote:
>
> Joakim,
>
> On Thu, Mar 1, 2018 at 2:39 PM, Joakim Tjernlund
> <joakim.tjernlund@infinera.com> wrote:
> > From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
> >
> > Some Micron chips does not work well wrt Erase suspend for
> > boot blocks. This avoids the issue by not allowing Erase suspend
> > for the boot blocks for the 28F00AP30(1GBit) chip.
>
> Is this bug documented somewhere?
One would hope but no. We got confirmation of the problem from the supplier though
but nothing written.
Jocke
next prev parent reply other threads:[~2018-03-21 0:03 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 [this message]
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
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=1521590574.4790.268.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard.weinberger@gmail.com \
--cc=stable@vger.kernel.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