From: Boris Brezillon <boris.brezillon@bootlin.com>
To: NeilBrown <neil@brown.name>
Cc: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Marek Vasut <marek.vasut@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
"Brian Norris" <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mtd: spi-nor: clear Winbond Extended Address Reg on switch to 3-byte addressing.
Date: Sat, 21 Apr 2018 00:10:28 +0200 [thread overview]
Message-ID: <20180421001028.544f5d09@bbrezillon> (raw)
In-Reply-To: <87efj9pnyk.fsf@notabene.neil.brown.name>
On Sat, 21 Apr 2018 07:28:19 +1000
NeilBrown <neil@brown.name> wrote:
> On Fri, Apr 20 2018, Boris Brezillon wrote:
>
> > Hi Neil,
> >
> > On Mon, 16 Apr 2018 09:42:30 +1000
> > NeilBrown <neil@brown.name> wrote:
> >
> >> Winbond spi-nor flash 32MB and larger have an 'Extended Address
> >> Register' as one option for addressing beyond 16MB (Macronix
> >> has the same concept, Spansion has EXTADD bits in the Bank Address
> >> Register).
> >>
> >> According to section
> >> 8.2.7 Write Extended Address Register (C5h)
> >>
> >> of the Winbond W25Q256FV data sheet (256M-BIT SPI flash)
> >>
> >> The Extended Address Register is only effective when the device is
> >> in the 3-Byte Address Mode. When the device operates in the 4-Byte
> >> Address Mode (ADS=1), any command with address input of A31-A24
> >> will replace the Extended Address Register values. It is
> >> recommended to check and update the Extended Address Register if
> >> necessary when the device is switched from 4-Byte to 3-Byte Address
> >> Mode.
> >>
> >> So the documentation suggests clearing the EAR after switching to
> >> 3-byte mode. Experimentation shows that the EAR is *always* one after
> >> the switch to 3-byte mode, so clearing the EAR is mandatory at
> >> shutdown for a subsequent 3-byte-addressed reboot to work.
> >>
> >> Note that some SOCs (e.g. MT7621) do not assert a reset line at normal
> >> reboot, so we cannot rely on hardware reset. The MT7621 does assert a
> >> reset line at watchdog-reset.
> >>
> >> Signed-off-by: NeilBrown <neil@brown.name>
> >
> > We should probably backport the fix. Can you add a Fixes and Cc-stable
> > tag?
>
> It's a bit weird having Fixes when this isn't a regression, but I guess
> it doesn't hurt.
Well, I thought you wanted this patch to be backported to stable
releases, hence my suggestion. Of course it's not a regression, since
the bug is here from the beginning, but nonetheless it's fixing a bug.
> I chose
> Fixes: 59b356ffd0b0 ("mtd: m25p80: restore the status of SPI flash when exiting")
> as this patch it useless without that one.
Not sure that's how Fixes should be used. IIUC, it should point to the
first commit where the bug was introduced, so I guess it's 0aa87b7563f1
("mtd: m25p80: add support for the windbond w25q256 chip") in this case.
Now, if you want to restrict the kernel releases this patch should be
backported to, you can use the '# vX.Y+' suffix in your Cc-stable tag.
>
> I also fixed the comment and have resent.
Thanks.
next prev parent reply other threads:[~2018-04-20 22:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:04 [PATCH] mtd: spi-nor: clear Extended Address Reg on switch to 3-byte addressing NeilBrown
2018-04-08 10:53 ` Marek Vasut
2018-04-08 21:56 ` NeilBrown
2018-04-09 21:58 ` Marek Vasut
2018-04-10 1:05 ` NeilBrown
2018-04-10 23:20 ` Marek Vasut
2018-07-23 18:25 ` Brian Norris
2018-07-23 21:45 ` NeilBrown
2018-07-23 22:17 ` Brian Norris
2018-07-23 22:23 ` NeilBrown
2018-04-10 23:13 ` Marek Vasut
2018-04-15 23:42 ` [PATCH v2] mtd: spi-nor: clear Winbond " NeilBrown
2018-04-20 19:54 ` Boris Brezillon
2018-04-20 21:26 ` [PATCH v3] " NeilBrown
2018-04-20 21:57 ` Marek Vasut
2018-04-20 22:54 ` [PATCH v4] " NeilBrown
2018-04-22 17:22 ` Boris Brezillon
2018-04-20 21:28 ` [PATCH v2] " NeilBrown
2018-04-20 22:10 ` Boris Brezillon [this message]
2018-04-20 22:51 ` NeilBrown
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=20180421001028.544f5d09@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=neil@brown.name \
--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