From: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx> v2: the check for UNLOCK_GLOBAL_BLOCK should be done the first thing in spi_nor_disable_block_protection(). We use it for a faster throughput, a single command cycle that unlocks the entire memory array. Fix it. This is similar 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. The Global Block-Protection Unlock command offers a single command cycle that unlocks the entire memory array. Prefer this method for higher throughput. Tested on the sst26vf064b flash using the atmel-quadspi driver. This has nothing to do with the move manufacturer out of the spi-nor core pursue, but depends on 'mtd: spi-nor: move manuf out of the core - batch 0' https://patchwork.ozlabs.org/project/linux-mtd/list/?series=127030 Tudor Ambarus (2): mtd: spi-nor: add Global Block Unlock support mtd: spi-nor: unlock global block protection on sst26vf064b drivers/mtd/spi-nor/spi-nor.c | 50 +++++++++++++++++++++++++++++++++++++++++-- include/linux/mtd/spi-nor.h | 1 + 2 files changed, 49 insertions(+), 2 deletions(-) -- 2.9.5 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/