kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch
authorJohn Thomson <git@johnthomson.fastmail.com.au>
Tue, 28 Sep 2021 10:51:56 +0000 (20:51 +1000)
committerKoen Vandeputte <koen.vandeputte@ncentric.com>
Wed, 29 Jun 2022 10:34:49 +0000 (12:34 +0200)
commitef69ab7a35a2ef5257aa2f718875b24856947c34
tree0fb469977130a3e58e8d370411917cd65252577b
parentaae3a8a254275f8be5c45d766ac7b5afb82a9fe6
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>
target/linux/generic/config-5.10
target/linux/generic/config-5.15
target/linux/generic/pending-5.10/470-mtd-spi-nor-support-limiting-4K-sectors-support-base.patch [deleted file]
target/linux/generic/pending-5.15/470-mtd-spi-nor-support-limiting-4K-sectors-support-base.patch [deleted file]
target/linux/layerscape/armv8_64b/config-5.10
target/linux/pistachio/config-5.10
target/linux/ramips/mt7620/config-5.10
target/linux/ramips/rt305x/config-5.10
target/linux/ramips/rt3883/config-5.10