Hi, John,
On Monday, March 2, 2020 8:25:48 PM EEST John Garry wrote:
> So do you know how we can tell if the part is s25fl129p1 or S25FS128S?
> Is it based on family id? For the part of my board, it has the same id
> according to "s25fl129p1" entry in the spi-nor driver, yet the SFDP
> signature is not present (signature reads as 0x4d182001 vs expected
0x4d182001 looks like the flash id, but in reversed order.
> 0x50444653). I printed the family id, and it is 81h, which seems to
> align with S25FS (which should support SFDP). Confused.
>
We can differentiate between flashes by the family id: 80h for FL-S and 81h
for FS-S. If I understood correctly your flash id is 0x01, 0x20, 0x18, 0x4d,
0x01, 0x81. According to the spansion datasheets, this should identify with a
s25fs128s1 entry. Please check the patch from below, let me know if it's ok.
> What's more, the spi-nor probe is failing for this part since I enabled
> quad spi. So I am interested to know if there is some differences
> between these part families for that.
In which conditions is it failing? Please open a separate thread.
Cheers,
ta
Author: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx>
Date: Sun Apr 26 17:59:23 2020 +0300
mtd: spi-nor: spansion: Add support for s25fs128s1
The old s25fl129p1 flash uses just five bytes for manufacturer and
device identification, while newer spansion flashes use six bytes.
s25fs128s1 was incorrectly identified as s25fl129p1. Use INFO6
to differentiate between them.
Signed-off-by: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx>
diff --git a/drivers/mtd/spi-nor/spansion.c b/drivers/mtd/spi-nor/spansion.c
index 88183eba8ac1..ea72f0e5be73 100644
--- a/drivers/mtd/spi-nor/spansion.c
+++ b/drivers/mtd/spi-nor/spansion.c
@@ -22,6 +22,9 @@ static const struct flash_info spansion_parts[] = {
{ "s25fl128s1", INFO6(0x012018, 0x4d0180, 64 * 1024, 256,
SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
USE_CLSR) },
+ { "s25fs128s1", INFO6(0x012018, 0x4d0181, 64 * 1024, 256,
+ SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
+ USE_CLSR) },
{ "s25fl256s0", INFO(0x010219, 0x4d00, 256 * 1024, 128,
SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
USE_CLSR) },
