From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <marek.vasut@gmail.com>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <boris.brezillon@bootlin.com>,
<richard@nod.at>, <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>
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: [PATCH v2 0/3] mtd: spi-nor: add Global Block Unlock support
Date: Tue, 11 Sep 2018 11:22:29 +0300 [thread overview]
Message-ID: <20180911082232.28678-1-tudor.ambarus@microchip.com> (raw)
To avoid inadvertent writes during power-up, SST26 flash memories are
write-protected by default after a power-on reset cycle. Unlock the serial
flash memory by using the Global Block Protection Unlock command - it offers
a single command cycle that unlocks the entire memory array.
v2:
- add Cyrille's reviewed-by tag
- add cover letter
- fix link to initial work done by Anurag Kumar Vulisha
Tudor Ambarus (3):
mtd: spi-nor: add Global Block Unlock support
mtd: spi-nor: unlock global block protection on sst26vf064b
mtd: spi-nor: add support for Microchip SST26 QSPI flash memories
drivers/mtd/spi-nor/spi-nor.c | 47 ++++++++++++++++++++++++++++++++++++++++++-
include/linux/mtd/spi-nor.h | 1 +
2 files changed, 47 insertions(+), 1 deletion(-)
--
2.9.4
next reply other threads:[~2018-09-11 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:22 Tudor Ambarus [this message]
2018-09-11 8:22 ` [PATCH v2 1/3] " Tudor Ambarus
2018-09-11 8:22 ` [PATCH v2 2/3] mtd: spi-nor: unlock global block protection on sst26vf064b Tudor Ambarus
2018-09-11 8:22 ` [PATCH v2 3/3] mtd: spi-nor: add support for Microchip SST26 QSPI flash memories Tudor Ambarus
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=20180911082232.28678-1-tudor.ambarus@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=anuragku@xilinx.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@microchip.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=nicolas.ferre@microchip.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®