spi95: Avoid automatic probing

It turned out that the read ID command for the ST/M95 family (0x83)
is a write command for AT45DB chips. We'll tag respective chips as
using a SPI95 command set, like we did for EDI, to avoid automatic
probing.

Change-Id: Ibdf364424ac9cd8a734507a05fe769f008f8178e
Signed-off-by: Nico Huber <nico.h@gmx.de>
Reviewed-on: https://review.sourcearcade.org/c/flashprog/+/75218
Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
diff --git a/flashchips.c b/flashchips.c
index 31bed4f..4f5b3eb 100644
--- a/flashchips.c
+++ b/flashchips.c
@@ -15629,6 +15629,7 @@
 		.page_size	= 256,
 		.feature_bits	= FEATURE_WRSR_WREN | FEATURE_NO_ERASE | FEATURE_ERASED_ZERO,
 		.tested		= TEST_OK_PREW,
+		.spi_cmd_set	= SPI95,
 		.probe		= probe_spi_st95,
 		.probe_timing	= TIMING_ZERO,
 		.block_erasers	=
diff --git a/include/flash.h b/include/flash.h
index bb31731..31d9a1c 100644
--- a/include/flash.h
+++ b/include/flash.h
@@ -248,7 +248,8 @@
 		/* SPI25 is very common. Keep it at zero so we don't have
 		   to specify it for each and every chip in the database.*/
 		SPI25 = 0,
-		SPI_EDI = 1,
+		SPI95,
+		SPI_EDI,
 	} spi_cmd_set;
 
 	int (*probe) (struct flashctx *flash);