From: <Tudor.Ambarus@microchip.com>
To: <marek.vasut@gmail.com>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <bbrezillon@kernel.org>,
<richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <anuragku@xilinx.com>,
<Cyrille.Pitchen@microchip.com>, <Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH 1/3] mtd: spi-nor: add Global Block Unlock support
Date: Thu, 14 Feb 2019 07:25:22 +0000 [thread overview]
Message-ID: <3626dadf-9fb1-b16d-d516-7e1e3056bc54@microchip.com> (raw)
In-Reply-To: <20180717162831.17947-1-tudor.ambarus@microchip.com>
On 07/17/2018 07:28 PM, Tudor Ambarus wrote:
> We can't determine this purely by manufacturer type and it's not
> autodetectable by anything like SFDP, so make a new flag for it:
> UNLOCK_GLOBAL_BLOCK.
>
> Note that 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,
> Winbound's W25Q128FV names it Global Block Unlock and
> Microchip's SST26VF064B names it Global Block Protection Unlock.
>
> Based on initial work done by Anurag Kumar Vulisha:
> https://patchwork.kernel.org/patch/7611271/
Time passed and now I think that this should be part of the individual block
lock support, as an optimization when one wants to unlock the entire flash
memory. Will rework it.
Cheers,
ta
prev parent reply other threads:[~2019-02-14 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 16:28 Tudor Ambarus
2018-07-17 16:28 ` [PATCH 2/3] mtd: spi-nor: unlock global block protection on sst26vf064b Tudor Ambarus
2018-07-17 16:28 ` [PATCH 3/3] mtd: spi-nor: add support for Microchip SST26 QSPI flash memories Tudor Ambarus
2018-07-25 12:26 ` [PATCH 1/3] mtd: spi-nor: add Global Block Unlock support Cyrille Pitchen
2019-02-14 7:25 ` 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=3626dadf-9fb1-b16d-d516-7e1e3056bc54@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Cyrille.Pitchen@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=anuragku@xilinx.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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
all inboxes | Powered by JetHome®