[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190717084745.19322-1-tudor.ambarus@microchip.com>
Date: Wed, 17 Jul 2019 08:47:56 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <vigneshr@...com>, <marek.vasut@...il.com>
CC: <dwmw2@...radead.org>, <computersforpeace@...il.com>,
<miquel.raynal@...tlin.com>, <richard@....at>,
<boris.brezillon@...labora.com>, <linux-mtd@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <Nicolas.Ferre@...rochip.com>,
<Tudor.Ambarus@...rochip.com>
Subject: [PATCH 0/5] mtd: spi-nor: write protection at power-up
From: Tudor Ambarus <tudor.ambarus@...rochip.com>
There is no functional change intended for the first 2 patches.
Patch 3 adds support for the Global Block Unlock command: a single
command cycle that unlocks the entire memory array.
Patch 4 unlocks the global block protection on sst26vf064b. This is
identical with what other nor flashes are doing by clearing the
block protection bits from the status register: disable the write
protection after a power-on reset cycle.
Patch 5 adds a Kconfig option to disable the write protection at
power-up. This permits users to choose if they want the write
protection at power-up enabled or not. Backward compatibility imposes
to disable the write protection at power-up, so the Kconfig option is
selected by default.
Tudor Ambarus (5):
mtd: spi-nor: fix description for int (*flash_is_locked)()
mtd: spi-nor: group the code about the write protection at power-up
mtd: spi-nor: add Global Block Unlock support
mtd: spi-nor: unlock global block protection on sst26vf064b
mtd: spi-nor: add Kconfig option to disable write protection at
power-up
drivers/mtd/spi-nor/Kconfig | 8 ++++++
drivers/mtd/spi-nor/spi-nor.c | 66 ++++++++++++++++++++++++++++++++-----------
include/linux/mtd/spi-nor.h | 9 +++---
3 files changed, 62 insertions(+), 21 deletions(-)
--
2.9.5
Powered by blists - more mailing lists