From a58986ca8b53d8c7a441397082f84edc7f47d19f Mon Sep 17 00:00:00 2001 From: Simon Glass Date: Tue, 6 Nov 2018 15:21:41 -0700 Subject: sf: Add a method to obtain the block-protect setting It is useful to obtain the block-protect setting of the SPI flash, so we know whether it is fully open or (perhaps partially) write-protected. Add a method for this. Update the sandbox driver to process this operation and add a test. Signed-off-by: Simon Glass --- test/dm/sf.c | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'test') diff --git a/test/dm/sf.c b/test/dm/sf.c index b23e7f8edd..35dce4e4c9 100644 --- a/test/dm/sf.c +++ b/test/dm/sf.c @@ -11,6 +11,7 @@ #include #include #include +#include #include #include #include @@ -45,6 +46,14 @@ static int dm_test_spi_flash(struct unit_test_state *uts) ut_assertok(spi_flash_read_dm(dev, 0, size, dst)); ut_assertok(memcmp(src, dst, size)); + /* Try the write-protect stuff */ + ut_assertok(uclass_first_device_err(UCLASS_SPI_EMUL, &emul)); + ut_asserteq(0, spl_flash_get_sw_write_prot(dev)); + sandbox_sf_set_block_protect(emul, 1); + ut_asserteq(1, spl_flash_get_sw_write_prot(dev)); + sandbox_sf_set_block_protect(emul, 0); + ut_asserteq(0, spl_flash_get_sw_write_prot(dev)); + /* * Since we are about to destroy all devices, we must tell sandbox * to forget the emulation device -- cgit v1.2.3