diff options
| author | Furquan Shaikh <furquan@chromium.org> | 2016-11-20 21:04:00 -0800 |
|---|---|---|
| committer | Furquan Shaikh <furquan@google.com> | 2016-11-22 17:32:09 +0100 |
| commit | c28984d9ea08e7d995ef9fc8064c10ec0c0d9d77 (patch) | |
| tree | c113582c3d2d8fb8d54a4c9a53375340fcc302d5 /src/northbridge/intel | |
| parent | 282c8322791800ee0d732fdaa5eb2cd8f7effd58 (diff) | |
| download | coreboot-c28984d9ea08e7d995ef9fc8064c10ec0c0d9d77.tar.xz | |
spi: Clean up SPI flash driver interface
RW flag was added to spi_slave structure to get around a requirement on
some AMD flash controllers that need to group together all spi volatile
operations (write/erase). This rw flag is not a property or attribute of
the SPI slave or controller. Thus, instead of saving it in spi_slave
structure, clean up the SPI flash driver interface. This allows
chipsets/mainboards (that require volatile operations to be grouped) to
indicate beginning and end of such grouped operations.
New user APIs are added to allow users to perform probe, read, write,
erase, volatile group begin and end operations. Callbacks defined in
spi_flash structure are expected to be used only by the SPI flash
driver. Any chipset that requires grouping of volatile operations can
select the newly added Kconfig option SPI_FLASH_HAS_VOLATILE_GROUP and
define callbacks for chipset_volatile_group_{begin,end}.
spi_claim_bus/spi_release_bus calls have been removed from the SPI flash
chip drivers which end up calling do_spi_flash_cmd since it already has
required calls for claiming and releasing SPI bus before performing a
read/write operation.
BUG=None
BRANCH=None
TEST=Compiles successfully.
Change-Id: Idfc052e82ec15b6c9fa874cee7a61bd06e923fbf
Signed-off-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-on: https://review.coreboot.org/17462
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/northbridge/intel')
| -rw-r--r-- | src/northbridge/intel/common/mrc_cache.c | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/src/northbridge/intel/common/mrc_cache.c b/src/northbridge/intel/common/mrc_cache.c index 4c3ee5d43c..a15812311b 100644 --- a/src/northbridge/intel/common/mrc_cache.c +++ b/src/northbridge/intel/common/mrc_cache.c @@ -212,7 +212,8 @@ static void update_mrc_cache(void *unused) "Need to erase the MRC cache region of %d bytes at %p\n", cache_size, cache_base); - flash->erase(flash, to_flash_offset(flash, cache_base), cache_size); + spi_flash_erase(flash, to_flash_offset(flash, cache_base), + cache_size); /* we will start at the beginning again */ cache = cache_base; @@ -220,8 +221,8 @@ static void update_mrc_cache(void *unused) // 4. write mrc data with flash->write() printk(BIOS_DEBUG, "Finally: write MRC cache update to flash at %p\n", cache); - ret = flash->write(flash, to_flash_offset(flash, cache), - current->mrc_data_size + sizeof(*current), current); + ret = spi_flash_write(flash, to_flash_offset(flash, cache), + current->mrc_data_size + sizeof(*current), current); if (ret) printk(BIOS_WARNING, "Writing the MRC cache failed with ret %d\n", |