From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <vigneshr@ti.com>, Tudor Ambarus <tudor.ambarus@microchip.com>,
<p.yadav@ti.com>, <michael@walle.cc>
Cc: <richard@nod.at>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Kavyasree.Kotagiri@microchip.com>, <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v3 1/2] mtd: spi-nor: Add Global Block Unlock command
Date: Fri, 5 Feb 2021 15:31:33 +0200 [thread overview]
Message-ID: <161253178923.670759.16987268553514371903.b4-ty@microchip.com> (raw)
In-Reply-To: <20210121110546.382633-1-tudor.ambarus@microchip.com>
On Thu, 21 Jan 2021 13:05:45 +0200, Tudor Ambarus wrote:
> The Global Block Unlock command has different names depending
> on the manufacturer, but always the same command value: 0x98.
> Macronix's MX25U12835F names it Gang Block Unlock, Winbond's
> W25Q128FV names it Global Block Unlock and Microchip's
> SST26VF064B names it Global Block Protection Unlock.
>
> Used in the Individual Block Protection mode, which is mutually
> exclusive with the Block Protection mode (BP0-3).
Applied to spi-nor/next, thanks!
[1/2] mtd: spi-nor: Add Global Block Unlock command
https://git.kernel.org/mtd/c/a7a5acba0e06
[2/2] mtd: spi-nor: sst: Add support for Global Unlock on sst26vf
https://git.kernel.org/mtd/c/75386810d3a6
Best regards,
--
Tudor Ambarus <tudor.ambarus@microchip.com>
prev parent reply other threads:[~2021-02-05 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 11:05 Tudor Ambarus
2021-01-21 11:05 ` [PATCH v3 2/2] mtd: spi-nor: sst: Add support for Global Unlock on sst26vf Tudor Ambarus
2021-01-21 11:19 ` Michael Walle
2021-02-05 13:31 ` Tudor Ambarus [this message]
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=161253178923.670759.16987268553514371903.b4-ty@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--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
all inboxes | Powered by JetHome®