Change in flashrom[staging]: flashchips: use 4BA direct erase functions for MX25L256

[David Hendricks (Code Review)]

David Hendricks has uploaded a new change for review. ( https://review.coreboot.org/19859 )

Change subject: flashchips: use 4BA direct erase functions for MX25L256
......................................................................

flashchips: use 4BA direct erase functions for MX25L256

When flashing via Dediprog SF600, the 4BYTE bit on my MX25L25635F
kept getting reset. To avoid having to set it each time we do an
erase operation (and incur the additional overhead), switch
MX25L25635F to use the "direct" 4BA erase instructions instead.

Change-Id: Ib3694eee96b5c082924fd3a9f63ea92830f896ce
Signed-off-by: David Hendricks 
---
M flashchips.c
1 file changed, 4 insertions(+), 3 deletions(-)

git pull ssh://review.coreboot.org:29418/flashrom refs/changes/59/19859/1

diff --git a/flashchips.c b/flashchips.c
index 1e6f4a4..b065537 100644
--- a/flashchips.c
+++ b/flashchips.c
@@ -25,6 +25,7 @@
 #include "flash.h"
 #include "flashchips.h"
 #include "chipdrivers.h"
+#include "spi4ba.h"

/**
  * List of supported flash chips.
@@ -8067,13 +8068,13 @@
    	{
    		{
    			.eraseblocks = { {4 * 1024, 8192} },
-				.block_erase = spi_block_erase_20_4ba,
+				.block_erase = spi_block_erase_21_4ba_direct,
    		}, {
    			.eraseblocks = { {32 * 1024, 1024} },
-				.block_erase = spi_block_erase_52_4ba,
+				.block_erase = spi_block_erase_5c_4ba_direct,
    		}, {
    			.eraseblocks = { {64 * 1024, 512} },
-				.block_erase = spi_block_erase_d8_4ba,
+				.block_erase = spi_block_erase_dc_4ba_direct,
    		}, {
    			.eraseblocks = { {32 * 1024 * 1024, 1} },
    			.block_erase = spi_block_erase_60,