Hi Alexander, On Mon, 26 Nov 2018 13:04:45 +0000 "Sverdlin, Alexander (Nokia - DE/Ulm)" <alexander.sverdlin@xxxxxxxxx> wrote: > Hello Tudor and all, > > On 26/11/2018 13:45, Tudor.Ambarus@xxxxxxxxxxxxx wrote: > > From: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx> > > > > BFPT advertises all the erase types supported by all the possible > > map configurations. Mask out the erase types that are not supported > > by the current map configuration. > > > > Backward compatibility test done on sst26vf064b. > > > > Fixes: b038e8e3be72 ("mtd: spi-nor: parse SFDP Sector Map Parameter Table") > > Reported-by: Alexander Sverdlin <alexander.sverdlin@xxxxxxxxx> > > I've verified the erasesize, partitioning and erase function of the S25FS128S > and all the above is at least back to pre-SFDP state. > > So the patch works as intended and it's > Tested-by: Alexander Sverdlin <alexander.sverdlin@xxxxxxxxx> > > There is still a regression with write when S25FS128S is used with SFDP > because SFDP of the S25FS128S is just broken. It advertises 512 bytes > of write page size but factory delivery configuration wraps the address > on 256 bytes boundary. I found no way to fetch this configuration in a > vendor-neutral way (or JEDEC-conform way). Which means, S25FS128S > could be the first user of SPI_NOR_SKIP_SFDP flag :\. You might be interested in my work around SPI NOR fixups[1]. I added a few fixup hooks that can be implemented by manufacturer drivers (a new concept) or on a per-chip basis. Looks like you'd need to implement a ->post_bfpt() fixup hook for this particular chip (see what's been done for this Macronix chip [2]). Regards, Boris [1]https://github.com/bbrezillon/linux-0day/commits/spi-nor/manuf-drv [2]https://github.com/bbrezillon/linux-0day/commit/b29625fdc55fa8ccfd4299904d727b44f8382c18 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/