From 3d76865fd50ab9b28f367ed27b19d8746548cdb1 Mon Sep 17 00:00:00 2001 From: Edward O'Callaghan Date: Thu, 5 Jan 2023 14:50:30 +1100 Subject: tests/chip: Add non-aligned write within a region unit-test A written region that is sized below that of the erasure granularity can result in a incorrectly read region that does not include prior content within the region before the write op. This was dealt with in ChromeOS downstream by expanding out the read to match the erase granularity however does not seem to impact upstream. Add a unit-test to avoid regression as this is important behaviour to cover. Change-Id: Id3ce5cd1936f0f348d34a6c77cee15e27a5c353f Signed-off-by: Edward O'Callaghan Reviewed-on: https://review.coreboot.org/c/flashrom/+/71659 Reviewed-by: Sam McNally Reviewed-by: Evan Benn Tested-by: build bot (Jenkins) --- tests/tests.h | 1 + 1 file changed, 1 insertion(+) (limited to 'tests/tests.h') diff --git a/tests/tests.h b/tests/tests.h index 6a12fdb0..bdcfdae9 100644 --- a/tests/tests.h +++ b/tests/tests.h @@ -80,6 +80,7 @@ void read_chip_test_success(void **state); void read_chip_with_dummyflasher_test_success(void **state); void write_chip_test_success(void **state); void write_chip_with_dummyflasher_test_success(void **state); +void write_nonaligned_region_with_dummyflasher_test_success(void **state); void verify_chip_test_success(void **state); void verify_chip_with_dummyflasher_test_success(void **state); -- cgit v1.2.3