[U-Boot] [PATCH RFT 0/3] spi-nor: spi-nor-ids: Fix 4 Byte addressing for n25q256 and n25q512*
Eugeniy.Paltsev at synopsys.com
Tue Sep 24 17:23:15 UTC 2019
I've check this patches on top of 31e086e460f.
The read/write/erase seems to work.
However, as I can see 'sf protect lock' doesn't work - it finish successfully but the area remains unlocked.
As I remember It worked with old u-boot spi-nor code, but I need to check it.
From: Vignesh Raghavendra <vigneshr at ti.com>
Sent: Tuesday, September 24, 2019 08:56
To: Jagan Teki; Eugeniy Paltsev; Ashish Kumar; Simon Goldschmidt
Cc: Vignesh Raghavendra; u-boot at lists.denx.de; Tom Rini; Alexey Brodkin
Subject: [PATCH RFT 0/3] spi-nor: spi-nor-ids: Fix 4 Byte addressing for n25q256 and n25q512*
This series removes SPI_NOR_4B_OPCODES flags from legacy variants of
n25q256* and n25q512* and adds entries for newer variants of those
flashes that support 4 Byte opcodes.
I don't have the flash devices. So its only compile tested.
I would greatly appreciate if you could test these patches and make sure
4 Byte opcodes are being used. (Probably by enabling/adding prints to
cmd->opcode in spi_mem_exec_op() in drivers/spi/spi-mem.c
Could you test this series on top of latest u-boot master and confirm
that your test cases still work?
Vignesh Raghavendra (3):
spi-nor: spi-nor-ids: Disable SPI_NOR_4B_OPCODES for n25q512* and
spi-nor: spi-nor-ids: Rename mt25qu512a entry
spi-nor: spi-nor-ids: Add entries for newer variants of n25q256* and
drivers/mtd/spi/spi-nor-ids.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
More information about the U-Boot