Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "vigneshr@ti.com" <vigneshr@ti.com>,
	"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] mtd: cfi_cmdset_0002: Use status register where possible
Date: Thu, 5 Nov 2020 16:44:52 +0000	[thread overview]
Message-ID: <5928a41bec2fe977085cbea0f69413c684950d58.camel@infinera.com> (raw)
In-Reply-To: <1af99b7d-e388-3c41-a8d8-9f82067ae857@ti.com>

On Thu, 2020-11-05 at 21:34 +0530, Vignesh Raghavendra wrote:
> 
> On 11/4/20 3:23 PM, Joakim Tjernlund wrote:
> > On Wed, 2020-11-04 at 11:12 +0530, Vignesh Raghavendra wrote:
> > > Hi Joakim
> > > 
> > > On 10/31/20 4:56 PM, Joakim Tjernlund wrote:
> > > > On Fri, 2020-10-30 at 19:52 +0100, Miquel Raynal wrote:
> > > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> > > > > 
> > > > > 
> [...]
> > > commit 4844ef80305d ("mtd: cfi_cmdset_0002: Add support for polling
> > > status register") was added in 5.3 and therefore is part of 5.4. But
> > > note that this is a "new feature" and therefore won't be backported to
> > > kernels older than 5.3.
> > 
> > Oh, my memory is off then, sorry.
> > 
> > > Similarly, this patch (when accepted) is not a candidate for stable
> > > kernel backports because the intention of enabling polling status
> > > register for Write Completion is to enable flashes that "don't" support
> > > DQ polling at all (mainly HyperFlash).
> > > Enabling this for all flashes that support the feature is not a bug fix
> > > IMO. Also, there isn't enough testing to prove that feature works for
> > > all CFI NOR flashes on all platforms and therefore would be risky to be
> > > backported to stable kernels.
> > 
> > This is 2 things,
> >  1. making it possible to use Hyper flash (HW enablement)
> >  2. improving the flash driver to function more precise(getting an accurate error rather than a TMO) for most AMD flashes.
> > 
> > 1. happens on a regular basis in stable.
> > 2. can be discussed for stable but should at least go into master now that status has been in there for a while
> > 
> 
> Yes, but my objection is that there has not been enough testing to prove
> that its safe to backport to stable kernels and there is nothing that's
> broken in older kernels which this patch fixes.

Semi broken though. I stumbled upon some erase failures that just resulted in a super long TMO error
rather than report a failure directly(the page was locked).

There I no way to improve upon error handling without your status updates and this is
the main reason I want your patches backported to 4.19 as well.

My patch can be dropped for stable, giving it time to mature in master though.

 Jocke
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-11-05 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 15:45 [PATCH] mtd: cfi_cmdset_0002: Use status register where possible Joakim Tjernlund
2020-10-30 17:47 ` Miquel Raynal
2020-10-30 18:39   ` Joakim Tjernlund
2020-10-30 18:52     ` Miquel Raynal
2020-10-31 11:26       ` Joakim Tjernlund
2020-11-04  5:42         ` Vignesh Raghavendra
2020-11-04  9:53           ` Joakim Tjernlund
2020-11-05 16:04             ` Vignesh Raghavendra
2020-11-05 16:44               ` Joakim Tjernlund [this message]
2020-11-05 15:57 ` Vignesh Raghavendra

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=5928a41bec2fe977085cbea0f69413c684950d58.camel@infinera.com \
    --to=joakim.tjernlund@infinera.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=stable@vger.kernel.org \
    --cc=vigneshr@ti.com \
    /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