mtd: spi-nor: Update mt25q/n25q entries
Subsystems (2)
Vignesh Raghavendra
maintainercover mtd: spi-nor: Update mt25q/n25q entries
First patch splits n25q512a and mt25qu512a into two as they are different devices. Second patch adds support for more mt25q devices and last patch adds USE_FSR flag for n25q entries where missing.
Tested with mt25qu512a flash
Vignesh Raghavendra (3):
mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
mtd: spi-nor: Add entries for mt25q variants
mtd: spi-nor: Add USE_FSR flag for n25q* entries
drivers/mtd/spi-nor/spi-nor.c | 31 +++++++++++++++++++++++-------- 1 file changed, 23 insertions(+), 8 deletions(-)
Signature · 1 line
2.24.0
Vignesh Raghavendra
maintainerPATCH 1/3 mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
mt25q family is different from n25q family of devices, even though manf ID and device IDs are same. mt25q flash has bit 6 set in 5th byte of READ ID response which can be used to distinguish it from n25q variant. mt25q flashes support stateless 4 Byte addressing opcodes where as n25q flashes don't. Therefore, have two separate entries for mt25qu512a and n25q512a.
--- drivers/mtd/spi-nor/spi-nor.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/mtd/spi-nor/spi-nor.c +5 -4
@@ -2459,15 +2459,16 @@ static const struct flash_info spi_nor_ids[] = { { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q512ax3", INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) }, + { "mt25qu512a", INFO6(0x20bb20, 0x104400, 64 * 1024, 1024, +SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, + { "n25q512a", INFO(0x20bb20, 0, 64 * 1024, 1024, SECT_4K | + SPI_NOR_QUAD_READ) }, { "n25q00", INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "n25q00a", INFO(0x20bb21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "mt25ql02g", INFO(0x20ba22, 0, 64 * 1024, 4096,SECT_4K |USE_FSR |SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, - { "mt25qu512a (n25q512a)", INFO(0x20bb20, 0, 64 * 1024, 1024, -SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | -SPI_NOR_QUAD_READ | - SPI_NOR_4B_OPCODES) }, { "mt25qu02g", INFO(0x20bb22, 0, 64 * 1024, 4096, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, /* Micron */
Signature · 1 line
2.24.0
RE: [EXT] [PATCH 1/3] mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
Hi Vignesh,
Quoted 32 lines
-----Original Message-----
From: Vignesh Raghavendra <[email protected]>
Sent: Thursday, December 5, 2019 12:30 PM
To: Tudor Ambarus <[email protected]>
Cc: Miquel Raynal <[email protected]>; Richard Weinberger <[email protected]>; Vignesh Raghavendra <[email protected]>; Ashish Kumar <[email protected]>; [email protected]; linux- [email protected]; John Garry <[email protected]>
Subject: [EXT] [PATCH 1/3] mtd: spi-nor: Split mt25qu512a (n25q512a) entry into twoCaution: EXT Email
mt25q family is different from n25q family of devices, even though manf ID and device IDs are same. mt25q flash has bit 6 set in 5th byte of READ ID response which can be used to distinguish it from n25q variant. mt25q flashes support stateless 4 Byte addressing opcodes where as n25q flashes don't. Therefore, have two separate entries for mt25qu512a and n25q512a.
Fixes 9607af6f857f ("mtd: spi-nor: Rename "n25q512a" to "mt25qu512a(n25q512a)"")
Signed-off-by Vignesh Raghavendra <[email protected]>--- drivers/mtd/spi-nor/spi-nor.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)drivers/mtd/spi-nor/spi-nor.c +0
-0
drivers/mtd/spi-nor/spi-nor.c static const struct flash_info spi_nor_ids[] = { · line 2467
Quoted 9 lines
drivers/mtd/spi-nor/spi-nor.c +3
-0@@ -2459,15 +2459,16 @@ static const struct flash_info spi_nor_ids[] = { {"n25q256a" ,INFO (0x20ba19 ,0 ,64 *1024 ,512 ,SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q512ax3", INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) }, + { "mt25qu512a", INFO6(0x20bb20, 0x104400, 64 * 1024, 1024, +SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
It seems you have moved back to my original patch [1], wrt mt25qu512a.
Regards
Ashish
Quoted 16 lines
drivers/mtd/spi-nor/spi-nor.c +2
-4+ {"n25q512a" ,INFO (0x20bb20 ,0 ,64 *1024 ,1024 ,SECT_4K | + SPI_NOR_QUAD_READ) }, { "n25q00", INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "n25q00a", INFO(0x20bb21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "mt25ql02g", INFO(0x20ba22, 0, 64 * 1024, 4096,SECT_4K |USE_FSR |SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, - { "mt25qu512a (n25q512a)", INFO(0x20bb20, 0, 64 * 1024, 1024, -SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | -SPI_NOR_QUAD_READ | - SPI_NOR_4B_OPCODES) }, { "mt25qu02g", INFO(0x20bb22, 0, 64 * 1024, 4096, SECT_4K | USE_FSR |
SPI_NOR_QUAD_READ|NO_CHIP_ERASE) },
Quoted 3 lines
/* Micron */--
2.24.0
Vignesh Raghavendra
maintainerRe: [EXT] [PATCH 1/3] mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
Quoted 1 line · Ashish Kumar
Hi Vignesh,
[...]
Quoted 19 lines
Quoted 8 lines
drivers/mtd/spi-nor/spi-nor.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)drivers/mtd/spi-nor/spi-nor.c +0
-0drivers/mtd/spi-nor/spi-nor.c static const struct flash_info spi_nor_ids[] = { · line 2467
Quoted 9 lines
drivers/mtd/spi-nor/spi-nor.c +3
-0@@ -2459,15 +2459,16 @@ static const struct flash_info spi_nor_ids[] = { {"n25q256a" ,INFO (0x20ba19 ,0 ,64 *1024 ,512 ,SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q512ax3", INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) }, + { "mt25qu512a", INFO6(0x20bb20, 0x104400, 64 * 1024, 1024, +SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },It seems you have moved back to my original patch [1], wrt mt25qu512a.
Yes, it seems like n25q and mt25q are not really same... mt25q supports stateless 4 byte addressing opcodes where as n25q does not. Hence we cannot add SPI_NOR_4B_OPCODES to n25q's idcodes.
This patch is outcome of from U-Boot discussion here (I believe you were cc'd as well):
https://patchwork.ozlabs.org/patch/1160501/
Regards
Vignesh
Quoted 23 lines
Regards
AshishQuoted 16 lines
drivers/mtd/spi-nor/spi-nor.c +2
-4+ {"n25q512a" ,INFO (0x20bb20 ,0 ,64 *1024 ,1024 ,SECT_4K | + SPI_NOR_QUAD_READ) }, { "n25q00", INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "n25q00a", INFO(0x20bb21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "mt25ql02g", INFO(0x20ba22, 0, 64 * 1024, 4096,SECT_4K |USE_FSR |SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, - { "mt25qu512a (n25q512a)", INFO(0x20bb20, 0, 64 * 1024, 1024, -SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | -SPI_NOR_QUAD_READ | - SPI_NOR_4B_OPCODES) }, { "mt25qu02g", INFO(0x20bb22, 0, 64 * 1024, 4096, SECT_4K | USE_FSR |
SPI_NOR_QUAD_READ|NO_CHIP_ERASE) },Quoted 3 lines
/* Micron */--
2.24.0
Vignesh Raghavendra
maintainerPATCH 2/3 mtd: spi-nor: Add entries for mt25q variants
In reply to Vignesh RaghavendraAdd entries for mt25q*256a and mt25q*512a flashes. These are similar to existing n25q variants but support stateless 4 byte addressing opcodes
--- drivers/mtd/spi-nor/spi-nor.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/mtd/spi-nor/spi-nor.c +9 -0
@@ -2456,8 +2456,17 @@ static const struct flash_info spi_nor_ids[] = { { "n25q064a", INFO(0x20bb17, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_QUAD_READ) }, + { "mt25ql256a", INFO6(0x20ba19, 0x104400, 64 * 1024, 512, +SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, + { "mt25qu256a", INFO6(0x20bb19, 0x104400, 64 * 1024, 512, +SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_QUAD_READ) }, + { "mt25ql512a", INFO6(0x20ba20, 0x104400, 64 * 1024, 1024, +SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, { "n25q512ax3", INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) }, { "mt25qu512a", INFO6(0x20bb20, 0x104400, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_DUAL_READ |
Signature · 1 line
2.24.0
Vignesh Raghavendra
maintainerPATCH 3/3 mtd: spi-nor: Add USE_FSR flag for n25q* entries
In reply to Vignesh RaghavendraAdd USE_FSR flag to all variants of n25q entries that support Flag Status Register.
--- drivers/mtd/spi-nor/spi-nor.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)
drivers/mtd/spi-nor/spi-nor.c +10 -5
@@ -2454,16 +2454,21 @@ static const struct flash_info spi_nor_ids[] = { { "n25q032a", INFO(0x20bb16, 0, 64 * 1024, 64, SPI_NOR_QUAD_READ) }, { "n25q064", INFO(0x20ba17, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q064a", INFO(0x20bb17, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_QUAD_READ) }, - { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_QUAD_READ) }, - { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_QUAD_READ) }, + { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, SECT_4K | + USE_FSR | SPI_NOR_QUAD_READ) }, + { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, SECT_4K | + USE_FSR | SPI_NOR_QUAD_READ) }, { "mt25ql256a", INFO6(0x20ba19, 0x104400, 64 * 1024, 512,SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, - { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, + { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | +USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ) }, { "mt25qu256a", INFO6(0x20bb19, 0x104400, 64 * 1024, 512,SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, - { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_QUAD_READ) }, + { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | + USE_FSR | SPI_NOR_QUAD_READ) }, { "mt25ql512a", INFO6(0x20ba20, 0x104400, 64 * 1024, 1024,SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
@@ -2472,7 +2477,7 @@ static const struct flash_info spi_nor_ids[] = {SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, { "n25q512a", INFO(0x20bb20, 0, 64 * 1024, 1024, SECT_4K | - SPI_NOR_QUAD_READ) }, + USE_FSR | SPI_NOR_QUAD_READ) }, { "n25q00", INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "n25q00a", INFO(0x20bb21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "mt25ql02g", INFO(0x20ba22, 0, 64 * 1024, 4096,
Signature · 1 line
2.24.0
Re: [PATCH 3/3] mtd: spi-nor: Add USE_FSR flag for n25q* entries
Quoted 4 lines · Vignesh Raghavendra
Add
USE_FSRflag to all variants of n25q entries that support Flag Status Register.Signed-off-by Vignesh Raghavendra <[email protected]>
Quoted 44 lines
--- drivers/mtd/spi-nor/spi-nor.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)drivers/mtd/spi-nor/spi-nor.c +10
-5@@ -2454,16 +2454,21 @@ static const struct flash_info spi_nor_ids[] = { { "n25q032a", INFO(0x20bb16, 0, 64 * 1024, 64, SPI_NOR_QUAD_READ) }, { "n25q064", INFO(0x20ba17, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_QUAD_READ) }, { "n25q064a", INFO(0x20bb17, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_QUAD_READ) }, - { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_QUAD_READ) }, - { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_QUAD_READ) }, + { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, SECT_4K | + USE_FSR | SPI_NOR_QUAD_READ) }, + { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, SECT_4K | + USE_FSR | SPI_NOR_QUAD_READ) }, { "mt25ql256a", INFO6(0x20ba19, 0x104400, 64 * 1024, 512,SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, - { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, + { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | +USE_FSR |SPI_NOR_DUAL_READ | + SPI_NOR_QUAD_READ) }, { "mt25qu256a", INFO6(0x20bb19, 0x104400, 64 * 1024, 512,SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, - { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_QUAD_READ) }, + { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | + USE_FSR | SPI_NOR_QUAD_READ) }, { "mt25ql512a", INFO6(0x20ba20, 0x104400, 64 * 1024, 1024,SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },@@ -2472,7 +2477,7 @@ static const struct flash_info spi_nor_ids[] = {SECT_4K |USE_FSR |SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, { "n25q512a", INFO(0x20bb20, 0, 64 * 1024, 1024, SECT_4K | - SPI_NOR_QUAD_READ) }, + USE_FSR | SPI_NOR_QUAD_READ) }, { "n25q00", INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "n25q00a", INFO(0x20bb21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, { "mt25ql02g", INFO(0x20ba22, 0, 64 * 1024, 4096,
Re: [PATCH 3/3] mtd: spi-nor: Add USE_FSR flag for n25q* entries
In reply to Vignesh RaghavendraHi, Vignesh,
Quoted 4 lines · Vignesh Raghavendra
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
Add
USE_FSRflag to all variants of n25q entries that support Flag Status Register.
On a first look, all Micron flashes define the Flag Status Register. Do you know if there are any Micron flash that don't support FSR? If not, would you be interested in doing some documentation work to check this?
I think we can do this more generic, always set SNOR_F_USE_FSR for micron flashes, like below. More, if FSR is specific just for Micron, we can get rid of the USE_FSR flag too.
Thanks, Vignesh.
drivers/mtd/spi-nor/spi-nor.c +1 -1
@@ -4595,7 +4595,7 @@ static void sst_set_default_init(struct spi_nor *nor)static void st_micron_set_default_init (struct spi_nor *nor) { - nor->flags |=SNOR_F_HAS_LOCK ; + nor->flags |=SNOR_F_HAS_LOCK |SNOR_F_USE_FSR ; nor->params.quad_enable =NULL ; nor->params.set_4byte = st_micron_set_4byte; }
Vignesh Raghavendra
maintainerRe: [PATCH 3/3] mtd: spi-nor: Add USE_FSR flag for n25q* entries
Hi Tudor,
Quoted 12 lines · On 10/12/19 10:11 pm, [email protected] wrote:
Hi, Vignesh,
Quoted 4 lines · Vignesh Raghavendra
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
Add
USE_FSRflag to all variants of n25q entries that support Flag Status Register.On a first look, all Micron flashes define the Flag Status Register. Do you know if there are any Micron flash that don't support FSR? If not, would you be interested in doing some documentation work to check this?
n25q and mt25 series support FSR but older m25p/m45p parts don't have FSR. I don't know any easy way of finding out if flash part is m25p type.
Quoted 4 lines
I think we can do this more generic, always set
SNOR_F_USE_FSRfor micron flashes, like below. More, if FSR is specific just for Micron, we can get rid of theUSE_FSRflag too.
AFAIK, FSR is definitely Micron specific (other flash vendors have different registers/bits providing similar information though).
Quoted 16 lines
Thanks, Vignesh.
drivers/mtd/spi-nor/spi-nor.c +1
-1@@ -4595,7 +4595,7 @@ static void sst_set_default_init(struct spi_nor *nor)static void st_micron_set_default_init (struct spi_nor *nor) { - nor->flags |=SNOR_F_HAS_LOCK ; + nor->flags |=SNOR_F_HAS_LOCK |SNOR_F_USE_FSR ; nor->params.quad_enable =NULL ; nor->params.set_4byte = st_micron_set_4byte; }
Signature · 6 lines
Regards Vignesh ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
Quoted 6 lines · Vignesh Raghavendra
First patch splits n25q512a and mt25qu512a into two as they are different devices. Second patch adds support for more mt25q devices and last patch adds
USE_FSRflag for n25q entries where missing.Tested with mt25qu512a flash
Quoted 7 lines
Vignesh Raghavendra (3):
mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
mtd: spi-nor: Add entries for mt25q variants
mtd: spi-nor: AddUSE_FSRflag for n25q* entriesdrivers/mtd/spi-nor/spi-nor.c | 31 +++++++++++++++++++++++-------- 1 file changed, 23 insertions(+), 8 deletions(-)
All applied, thanks.
ta