[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAEAJfAeBW_As1tF19xBVcdafBUdwEtPjupVEmBD4G4gU2OjVw@mail.gmail.com>
Date: Thu, 28 Jan 2016 11:42:45 -0300
From: Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
To: Brian Norris <computersforpeace@...il.com>
Cc: "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
Rafał Miłecki <zajec5@...il.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Bayi Cheng <bayi.cheng@...iatek.com>,
Marek Vasut <marex@...x.de>,
Daniel Kurtz <djkurtz@...omium.org>
Subject: Re: [PATCH 0/8] mtd: spi-nor: locking fixes and updates
On 28 January 2016 at 02:51, Brian Norris <computersforpeace@...il.com> wrote:
> Hi,
>
> These are an assortment of fixes and updates to the SPI NOR lock/unlock
> feature. The biggest new features are:
> (a) Status Register protection; I don't see why this shouldn't be enabled by
> default. See patch 4's description.
> (b) Bottom-block protection support (via TB status bit)
> (c) Lock/unlock support for a few Winbond flash
>
> Patch 7 (Top/Bottom protection support) is still an RFC, as I think it deserves
> a bit more work. But I'm just getting it out there, as it's been sitting on my
> plate for a while.
>
> Regards,
> Brian
>
> Brian Norris (8):
> mtd: spi-nor: wait for SR_WIP to clear on initial unlock
> mtd: spi-nor: guard against underflows in stm_is_locked_sr
> mtd: spi-nor: silently drop lock/unlock for already locked/unlocked
> region
> mtd: spi-nor: disallow further writes to SR if WP# is low
> mtd: spi-nor: use BIT() for flash_info flags
> mtd: spi-nor: add SPI_NOR_HAS_LOCK flag
> mtd: spi-nor: add TB (Top/Bottom) protect support
> mtd: spi-nor: support lock/unlock for a few Winbond chips
>
For all patches, except RFC 7/8:
Reviewed-by: Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
Powered by blists - more mailing lists