summaryrefslogtreecommitdiff
path: root/drivers/mtd/chips/cfi_cmdset_0001.c
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@bootlin.com>2023-11-04 13:49:52 +0300
committerMiquel Raynal <miquel.raynal@bootlin.com>2023-11-04 13:50:13 +0300
commit3a8ab4a13d17f2a16cd4f125e5238096c1c55149 (patch)
treec4074fc0b0fc15054d3fbd54220c0e426d1734ca /drivers/mtd/chips/cfi_cmdset_0001.c
parent565fe150624ee77dc63a735cc1b3bff5101f38a3 (diff)
parent6823a8383420263bc061865027836755615a275f (diff)
downloadlinux-3a8ab4a13d17f2a16cd4f125e5238096c1c55149.tar.xz
Merge tag 'spi-nor/for-6.7' into mtd/next
For SPI NOR we cleaned the flash info entries in order to have them slimmer and self explanatory. In order to make the entries as slim as possible, we introduced sane default values so that the actual flash entries don't need to specify them. We now use a flexible macro to specify the flash ID instead of the previous INFOx() macros that had hardcoded ID lengths. Instead of: - { "w25q512nwm", INFO(0xef8020, 0, 64 * 1024, 0) - OTP_INFO(256, 3, 0x1000, 0x1000) }, We now use: + .id = SNOR_ID(0xef, 0x80, 0x20), + .name = "w25q512nwm", + .otp = SNOR_OTP(256, 3, 0x1000, 0x1000), We also removed some flash entries: the very old Catalyst SPI EEPROMs that were introduced once with the SPI-NOR subsystem, and a Fujitsu MRAM. Both should use the at25 EEPROM driver. The latter even has device tree bindings for the at25 driver. We made sure that the conversion didn't introduce any unwanted changes by comparing the .rodata segment before and after the conversion. The patches landed in linux-next immediately after v6.6-rc2, we haven't seen any regressions yet. Apart of the autumn cleaning we introduced a new flash entry, at25ff321a, and added block protection support for mt25qu512a. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Diffstat (limited to 'drivers/mtd/chips/cfi_cmdset_0001.c')
0 files changed, 0 insertions, 0 deletions