[PATCH v3 1/2] mtd: spi-nor: Set the erase flag for multi-die

Michael Walle michael at walle.cc
Fri Oct 27 13:03:22 PDT 2023


>> Instead of manually passing the .flags = NO_CHIP_ERASE in the case
>> of multi-die SPI NOR flash, retrieve the information about the number of
>> dies directly from SFDP and set the SNOR_F_NO_OP_CHIP_ERASE flag in the
>> multi-die case.
>
>We don't have enough data from manufacturers to make such an assumption.
>And since this is not backed up by a standard, I'd like to stick to the
>.flags = NO_CHIP_ERASE for now

mh. we have two flashes which are multi die ones. as far as I remember. i checked the semper flash and it didn't support chip erase. also.. chip erase isn't a standard either and not backed by SFDP, correct? We shouldn't use it in the first place. So we might have a chance to fix that for multi die chips now. 

So as long as there isn't a multi die flash which supports 
chip erase, I'd like to keep the additional flags as minimal as possible. for the best case scenario it would just work out of the box with just SFDP, which is impossible if we need that no_chip_erase flag.

-michael 



More information about the linux-mtd mailing list