mtd: spi-nor: spansion: Add support for CY15V104QSN
Subsystems (2)
PATCH 1/1 mtd: spi-nor: spansion: Add support for CY15V104QSN
Infineon CY15V104QSN is 4Mbit serial SPI F-RAM device.
--- drivers/mtd/spi-nor/spansion.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/mtd/spi-nor/spansion.c +6 -0
@@ -922,6 +922,12 @@ static const struct flash_info spansion_nor_parts[] = { .size = SZ_512K, .sector_size = SZ_512K, .flags = SPI_NOR_NO_ERASE, + }, { + .id = SNOR_ID(0x50, 0x51, 0x80, 0x06, 0x00, 0x00), + .name = "cy15v104qsn", + .size = SZ_512K, + .sector_size = SZ_512K, + .flags = SPI_NOR_NO_ERASE, }, { .id = SNOR_ID(0x34, 0x2a, 0x1a, 0x0f, 0x03, 0x90), .name = "s25hl512t",
Signature · 5 lines
2.19.1 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
Quoted 1 line · LECOINTRE Philippe
Infineon CY15V104QSN is 4Mbit serial SPI F-RAM device.
Please consider moving this flash to the at25 EEPROM driver:
https://lore.kernel.org/linux-mtd/[email protected]/
Cheers,
ta
Quoted 14 lines
Signed-off-by Philippe Lecointre <[email protected]>Acked-by Simon Lenain <[email protected]>--- drivers/mtd/spi-nor/spansion.c | 6 ++++++ 1 file changed, 6 insertions(+)drivers/mtd/spi-nor/spansion.c +0
-0@@ -922,6 +922,12 @@ static const struct flash_info spansion_nor_parts[] = { .size = SZ_512K, .sector_size = SZ_512K,
drivers/mtd/spi-nor/spansion.c static const struct flash_info spansion_nor_parts[] = { · line 933
Quoted 10 lines
drivers/mtd/spi-nor/spansion.c +6
-0.flags = SPI_NOR_NO_ERASE, + }, { + .id = SNOR_ID(0x50, 0x51, 0x80, 0x06, 0x00, 0x00), + .name = "cy15v104qsn", + .size = SZ_512K, + .sector_size = SZ_512K, + .flags = SPI_NOR_NO_ERASE, }, { .id = SNOR_ID(0x34, 0x2a, 0x1a, 0x0f, 0x03, 0x90), .name = "s25hl512t",
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Classified as: {OPEN}
Hello,
Thank you for your feedback.
I encounter some issue attempting to use the at25 driver.
I am not able to read the flash ID with at25 driver because the chipselect appear to be deselected between the RDID command and the read data. The RDID command is not taken into account and the chip only reply with 0xff. With at25 driver, it use a spi_message containing two spi_transfer, one spi_transfer for the command and one spi_transfer for the read data. For some reason, this end up in .transfer_one() in the spi_controller driver of my SoC. With spi-nor driver, it use spi_mem_exec_op() which work well in my case.
It appear at25 driver can currently be used with Cypress FM25 chip and from some of the datasheet of this family it seems that the chipselect need to be driven low during the entire RDID sequence. Am I missing something here ?
Currently, the at25 driver assume a lot of property from the ID data (manufacturer and size) which don't seems to be relevant with the CY15V104QSN model. This chip is similar to cy15b104q and cy15v104q currently supported by spi-nor driver.
https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mtd/spi-nor/spansion.c?id=8a2644d5f3608822925c9204a3d19a8e3025fd4a
Also, I don't have access to at25 spi eeprom to validate any deep modifications on this driver if we need to do so according to the thread you are pointing to.
How can we handle this ?
Regards,
Philippe
{OPEN}
Quoted 36 lines
-----Original Message-----
From: Tudor Ambarus <[email protected]>
Sent: Thursday, March 6, 2025 11:54 AM
To: LECOINTRE Philippe <[email protected]>; Pratyush Yadav <[email protected]>; Michael Walle <[email protected]>; linux- [email protected]
Cc: LEJEUNE Sebastien <[email protected]>; LENAIN Simon <[email protected]>; RENAULT Xavier <[email protected]>
Subject: Re: [PATCH] mtd: spi-nor: spansion: Add support for CY15V104QSNQuoted 1 line · LECOINTRE Philippe
Infineon CY15V104QSN is 4Mbit serial SPI F-RAM device.
Please consider moving this flash to the at25 EEPROM driver:
https://lore.kernel.org/linux-mtd/20240604074231.1874972-1-
[email protected]/Cheers,
tadrivers/mtd/spi-nor/spansion.c static const struct flash_info spansion_nor_parts[]
Quoted 13 lines
Signed-off-by Philippe Lecointre <[email protected]>Acked-by Simon Lenain <[email protected]>--- drivers/mtd/spi-nor/spansion.c | 6 ++++++ 1 file changed, 6 insertions(+)(quoted diff) +0
-0
b/drivers/mtd/spi-nor/spansion.cindexbf08dbf5e742..32f8892d7afe100644drivers/mtd/spi-nor/spansion.c +0
-0@@ -922,6 +922,12 @@ static const struct flash_info spansion_nor_parts[]= {
Quoted 12 lines
drivers/mtd/spi-nor/spansion.c static const struct flash_info spansion_nor_parts[] = { · line 933
Quoted 12 lines
drivers/mtd/spi-nor/spansion.c +6
-0.size = SZ_512K, .sector_size = SZ_512K, .flags = SPI_NOR_NO_ERASE, + }, { + .id = SNOR_ID(0x50, 0x51, 0x80, 0x06, 0x00, 0x00), + .name = "cy15v104qsn", + .size = SZ_512K, + .sector_size = SZ_512K, + .flags = SPI_NOR_NO_ERASE, }, { .id = SNOR_ID(0x34, 0x2a, 0x1a, 0x0f, 0x03, 0x90), .name = "s25hl512t",
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Quoted 3 lines · LECOINTRE Philippe
Classified as: {OPEN}
Hello,
Hi,
Don't top post please, it's hard to follow the emails exchanged.
Quoted 2 lines
Thank you for your feedback.
you're welcome!
Quoted 4 lines
I encounter some issue attempting to use the at25 driver.
I am not able to read the flash ID with at25 driver because the chipselect appear to be deselected between the RDID command and the read data. The RDID command is not taken into account and the chip only reply with0xff. With at25 driver, it use aspi_messagecontaining twospi_transfer, onespi_transferfor the command and onespi_transferfor the read data. For some reason, this end up in .transfer_one() in thespi_controllerdriver of my SoC.
What spi controller driver, is it upstreamed?
Quoted 3 lines
With spi-nor driver, it use
spi_mem_exec_op()which work well in my case.
It appear at25 driver can currently be used with Cypress FM25 chip and from some of the datasheet of this family it seems that the chipselect need to be driven low during the entire RDID sequence. Am I missing something here ?
Splitting opcode, address, dummy and data per spi_transfers shall work, spi_mem_exec_op() does it too when the controller does not define mem_ops.
It probably just a bug somewhere, raising CS up between the transfers shall be fine.
Quoted 4 lines
Currently, the at25 driver assume a lot of property from the ID data (manufacturer and size) which don't seems to be relevant with the CY15V104QSN model. This chip is similar to cy15b104q and cy15v104q currently supported by spi-nor driver.
https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mtd/spi-nor/spansion.c?id=8a2644d5f3608822925c9204a3d19a8e3025fd4a
having those flashes in SPI NOR was a mistake. We can't just drop them as we'll break backward compatibility.
Quoted 3 lines
Also, I don't have access to at25 spi eeprom to validate any deep modifications on this driver if we need to do so according to the thread you are pointing to.
How can we handle this ?
You need to figure out why your flash doesn't work as expected and fix it. Is your controller spimem capable? If yes, try dropping the ctrl mem_ops and see if it behaves sane using SPI NOR and the controller using spi transfers. If it doesn't behave sane, then there's probably a problem into the controller driver.
Cheers,
ta
Quoted 43 lines
Regards,
Philippe{OPEN}
Quoted 36 lines
-----Original Message-----
From: Tudor Ambarus <[email protected]>
Sent: Thursday, March 6, 2025 11:54 AM
To: LECOINTRE Philippe <[email protected]>; Pratyush Yadav <[email protected]>; Michael Walle <[email protected]>; linux- [email protected]
Cc: LEJEUNE Sebastien <[email protected]>; LENAIN Simon <[email protected]>; RENAULT Xavier <[email protected]>
Subject: Re: [PATCH] mtd: spi-nor: spansion: Add support for CY15V104QSNQuoted 1 line · LECOINTRE Philippe
Infineon CY15V104QSN is 4Mbit serial SPI F-RAM device.
Please consider moving this flash to the at25 EEPROM driver:
https://lore.kernel.org/linux-mtd/20240604074231.1874972-1-
[email protected]/Cheers,
tadrivers/mtd/spi-nor/spansion.c static const struct flash_info spansion_nor_parts[]
Quoted 13 lines
Signed-off-by Philippe Lecointre <[email protected]>Acked-by Simon Lenain <[email protected]>--- drivers/mtd/spi-nor/spansion.c | 6 ++++++ 1 file changed, 6 insertions(+)(quoted diff) +0
-0
b/drivers/mtd/spi-nor/spansion.cindexbf08dbf5e742..32f8892d7afe100644drivers/mtd/spi-nor/spansion.c +0
-0@@ -922,6 +922,12 @@ static const struct flash_info spansion_nor_parts[]= {
Quoted 12 lines
Quoted 4 lines
Quoted 4 lines
drivers/mtd/spi-nor/spansion.c +1
-0.size = SZ_512K, .sector_size = SZ_512K, .flags = SPI_NOR_NO_ERASE, + }, {Quoted 8 lines
drivers/mtd/spi-nor/spansion.c static const struct flash_info spansion_nor_parts[] = { · line 933
Quoted 8 lines
drivers/mtd/spi-nor/spansion.c +5
-0+ .id = SNOR_ID(0x50, 0x51, 0x80, 0x06, 0x00, 0x00), + .name = "cy15v104qsn", + .size = SZ_512K, + .sector_size = SZ_512K, + .flags = SPI_NOR_NO_ERASE, }, { .id = SNOR_ID(0x34, 0x2a, 0x1a, 0x0f, 0x03, 0x90), .name = "s25hl512t",
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Classified as: {OPEN}
Hello,
{OPEN}
Quoted 30 lines
-----Original Message-----
From: Tudor Ambarus <[email protected]>
Sent: Thursday, March 20, 2025 9:47 AM
To: LECOINTRE Philippe <[email protected]>; Pratyush Yadav <[email protected]>; Michael Walle <[email protected]>; linux- [email protected]; Takahiro Kuwano <[email protected]>
Cc: LEJEUNE Sebastien <[email protected]>; LENAIN Simon <[email protected]>; RENAULT Xavier <[email protected]>
Subject: Re: [PATCH] mtd: spi-nor: spansion: Add support for CY15V104QSNQuoted 3 lines · LECOINTRE Philippe
Classified as: {OPEN}
Hello,
Hi,
Don't top post please, it's hard to follow the emails exchanged.
Quoted 2 lines
Thank you for your feedback.
you're welcome!
Quoted 3 lines
I encounter some issue attempting to use the at25 driver.
I am not able to read the flash ID with at25 driver because the chipselect
Quoted 8 lines
appear to be deselected between the RDID command and the read data. The RDID command is not taken into account and the chip only reply with
0xff.Quoted 1 line
With at25 driver, it use a
spi_messagecontaining twospi_transfer, one
spi_transferfor the command and onespi_transferfor the read data. For some reason, this end up in .transfer_one() in thespi_controllerdriver of my SoC.What spi controller driver, is it upstreamed?
The SoC use the upstream "snps,dw-apb-ssi" spi controller driver.
Quoted 5 lines
Quoted 3 lines
With spi-nor driver, it use
spi_mem_exec_op()which work well in my case. It appear at25 driver can currently be used with Cypress FM25 chip andfrom some of the datasheet of this family it seems that the chipselect need to be driven low during the entire RDID sequence.
Quoted 8 lines
Quoted 1 line
Am I missing something here ?
Splitting opcode, address, dummy and data per
spi_transfersshall work,spi_mem_exec_op()does it too when the controller does not definemem_ops.It probably just a bug somewhere, raising CS up between the transfers shall be fine.
Using an oscilloscope with spi protocol decode, it is the big difference I can see.
Quoted 18 lines
Quoted 2 lines
Currently, the at25 driver assume a lot of property from the ID data
(manufacturer and size) which don't seems to be relevant with the CY15V104QSN model.
Quoted 1 line
This chip is similar to cy15b104q and cy15v104q currently supported by spi-
nor driver.
Quoted 2 lines
https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/c
ommit/drivers/mtd/spi-nor/spansion.c?id=8a2644d5f3608822925c9204a3d19a
Quoted 1 line
8e3025fd4ahaving those flashes in SPI NOR was a mistake. We can't just drop them as we'll break backward compatibility.
Quoted 1 line
Also, I don't have access to at25 spi eeprom to validate any deep
modifications on this driver if we need to do so according to the thread you are pointing to.
Quoted 1 line
Quoted 7 lines
Quoted 1 line
How can we handle this ?
You need to figure out why your flash doesn't work as expected and fix it. Is your controller spimem capable? If yes, try dropping the ctrl
mem_opsand see if it behaves sane using SPI NOR and the controller using spi transfers. If it doesn't behave sane, then there's probably a problem into the controller driver.
Good advice !
I have commented out the dw_spi_init_mem_ops() function call in dw_spi_add_host() and I end up with the same result as at25 driver. spi-nor spi3.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
I need to investigate further on this issue.
The drawback is that our project is currently based on Linux 6.1 CIP kernel and I need some efforts to rebase on the current master. Until now, it wasn't an issue regarding the complexity of spi-nor modifications of the initial contribution. From what I see, there is not much changes on the spi controller drivers, probably more in the spi core.
If you have any other advice, I will be glad to have them.
Regards,
Philippe
Quoted 49 lines
Cheers,
taQuoted 46 lines
Regards,
Philippe{OPEN}
Quoted 39 lines
-----Original Message-----
From: Tudor Ambarus <[email protected]>
Sent: Thursday, March 6, 2025 11:54 AM
To: LECOINTRE Philippe <[email protected]>; Pratyush Yadav <[email protected]>; Michael Walle <[email protected]>; linux- [email protected]
Cc: LEJEUNE Sebastien <[email protected]>; LENAIN Simon <[email protected]>; RENAULT Xavier <[email protected]>
Subject: Re: [PATCH] mtd: spi-nor: spansion: Add support for CY15V104QSNQuoted 1 line · LECOINTRE Philippe
Infineon CY15V104QSN is 4Mbit serial SPI F-RAM device.
Please consider moving this flash to the at25 EEPROM driver:
https://lore.kernel.org/linux-mtd/20240604074231.1874972-1-
[email protected]/Cheers,
taQuoted 14 lines
Signed-off-by: Philippe Lecointre
<[email protected]>Acked-by Simon Lenain <[email protected]>--- drivers/mtd/spi-nor/spansion.c | 6 ++++++ 1 file changed, 6 insertions(+)(quoted diff) +0
-0
b/drivers/mtd/spi-nor/spansion.cindexbf08dbf5e742..32f8892d7afe100644drivers/mtd/spi-nor/spansion.c +0
-0@@ -922,6 +922,12 @@ static const struct flash_infoQuoted 1 line
spansion_nor_parts[]
= {
Quoted 12 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
drivers/mtd/spi-nor/spansion.c +1
-0.size = SZ_512K, .sector_size = SZ_512K, .flags = SPI_NOR_NO_ERASE, + }, {Quoted 8 lines
Quoted 8 lines
drivers/mtd/spi-nor/spansion.c static const struct flash_info spansion_nor_parts[] = { · line 933
Quoted 8 lines
drivers/mtd/spi-nor/spansion.c +5
-0+ .id = SNOR_ID(0x50, 0x51, 0x80, 0x06, 0x00, 0x00), + .name = "cy15v104qsn", + .size = SZ_512K, + .sector_size = SZ_512K, + .flags = SPI_NOR_NO_ERASE, }, { .id = SNOR_ID(0x34, 0x2a, 0x1a, 0x0f, 0x03, 0x90), .name = "s25hl512t",
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Quoted 55 lines · LECOINTRE Philippe
Quoted 10 lines
I encounter some issue attempting to use the at25 driver.
Quoted 1 line
I am not able to read the flash ID with at25 driver because the chipselect
appear to be deselected between the RDID command and the read data. The RDID command is not taken into account and the chip only reply with
0xff.Quoted 1 line
With at25 driver, it use a
spi_messagecontaining twospi_transfer, one
spi_transferfor the command and onespi_transferfor the read data. For some reason, this end up in .transfer_one() in thespi_controllerdriver of my SoC.What spi controller driver, is it upstreamed?
The SoC use the upstream "snps,dw-apb-ssi" spi controller driver.
Quoted 5 lines
Quoted 3 lines
With spi-nor driver, it use
spi_mem_exec_op()which work well in my case. It appear at25 driver can currently be used with Cypress FM25 chip andfrom some of the datasheet of this family it seems that the chipselect need to be driven low during the entire RDID sequence.
Quoted 8 lines
Quoted 1 line
Am I missing something here ?
Splitting opcode, address, dummy and data per
spi_transfersshall work,spi_mem_exec_op()does it too when the controller does not definemem_ops.It probably just a bug somewhere, raising CS up between the transfers shall be fine.
Using an oscilloscope with spi protocol decode, it is the big difference I can see.
Quoted 18 lines
Quoted 2 lines
Currently, the at25 driver assume a lot of property from the ID data
(manufacturer and size) which don't seems to be relevant with the CY15V104QSN model.
Quoted 1 line
This chip is similar to cy15b104q and cy15v104q currently supported by spi-
nor driver.
Quoted 2 lines
https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/c
ommit/drivers/mtd/spi-nor/spansion.c?id=8a2644d5f3608822925c9204a3d19a
Quoted 1 line
8e3025fd4ahaving those flashes in SPI NOR was a mistake. We can't just drop them as we'll break backward compatibility.
Quoted 1 line
Also, I don't have access to at25 spi eeprom to validate any deep
modifications on this driver if we need to do so according to the thread you are pointing to.
Quoted 1 line
Quoted 7 lines
Quoted 1 line
How can we handle this ?
You need to figure out why your flash doesn't work as expected and fix it. Is your controller spimem capable? If yes, try dropping the ctrl
mem_opsand see if it behaves sane using SPI NOR and the controller using spi transfers. If it doesn't behave sane, then there's probably a problem into the controller driver.
Quoted 3 lines
Good advice !
I have commented out thedw_spi_init_mem_ops()function call indw_spi_add_host()and I end up with the same result as at25 driver. spi-nor spi3.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
Can you plugin a different flash and test?
What frequency are you running the flash? Do things improve if you run it at 50 MHz for example?
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/