Skip to contentSkip to conversation

spi: intel: 64k erase is supported from Canon Lake and beyond

PATCH In review Mika Westerberg 2 participants 2 messages Aug 16, 2022 – Aug 22, 2022 SPI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: intel: 64k erase is supported from Canon Lake and beyond

The hardware sequencer in Intel Canon Lake and beyond supports also 64k erase command. The SPI-NOR core uses SFDP (Serial Flash Discovery Parameter) to figure out what the chip actually supports and only issues 64k erase if it is supported.

---
 drivers/spi/spi-intel.c | 1 +
 1 file changed, 1 insertion(+)
drivers/spi/spi-intel.c +1 -0
index 66063687ae27..c020b276e238 100644
@@ -1073,6 +1073,7 @@ static int intel_spi_init(struct intel_spi *ispi)
 		ispi->pregs = ispi->base + CNL_PR;
 		ispi->nregions = CNL_FREG_NUM;
 		ispi->pr_num = CNL_PR_NUM;
+		erase_64k = true;
 		break;
 
 	default:
Signature · 1 line
2.35.1
maintainer
#1 lore raw
Quoted 6 lines · Mika Westerberg

The hardware sequencer in Intel Canon Lake and beyond supports also 64k erase command. The SPI-NOR core uses SFDP (Serial Flash Discovery Parameter) to figure out what the chip actually supports and only issues 64k erase if it is supported.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: intel: 64k erase is supported from Canon Lake and beyond

      commit: 1d895be13af0d962bef67ba0ceaefbdc6954fe67

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark