diff options
| author | John Thomson <git@johnthomson.fastmail.com.au> | 2021-09-28 20:51:56 +1000 |
|---|---|---|
| committer | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2022-06-29 12:34:49 +0200 |
| commit | ef69ab7a35a2ef5257aa2f718875b24856947c34 (patch) | |
| tree | 0fb469977130a3e58e8d370411917cd65252577b /target/linux/bcm4908 | |
| parent | aae3a8a254275f8be5c45d766ac7b5afb82a9fe6 (diff) | |
| download | upstream-ef69ab7a35a2ef5257aa2f718875b24856947c34.tar.gz upstream-ef69ab7a35a2ef5257aa2f718875b24856947c34.tar.bz2 upstream-ef69ab7a35a2ef5257aa2f718875b24856947c34.zip | |
kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch
Since 4e0c54bc5bc8 ("kernel: add support for kernel 5.4"),
the spi-nor limit 4k erasesize to spi-nor chips below a configured size
patch has not functioned as intended.
For uniform erasesize SPI-NOR devices, both
nor->erase_opcode & mtd->erasesize are used in erase operations.
These are set before, and not modified by, this
CONFIG_MTD_SPI_NOR_USE_4K_SECTORS_LIMIT patch.
Thus, an SPI-NOR device with CONFIG_MTD_SPI_NOR_USE_4K_SECTORS will
always use 4k erasesize (where the device supports it).
If this patch was fixed to function as intended, there would be
cases where devices change from a 4K to a 64K erasesize.
Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
Diffstat (limited to 'target/linux/bcm4908')
0 files changed, 0 insertions, 0 deletions