leandrof/u-boot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

test: fastboot: Avoid using mmc1

Browse Source 
The bootflow tests need to use an MMC with an associated backing file
containing a filesystem. Update the fastboot tests to cope with this.

Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Simon Glass 2022-04-24 23:31:01 -06:00 committed by Tom Rini
parent 4e0710a2d0
commit 9bd2f62d12
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
test/dm/fastboot.c
View File

@ -81,9 +81,9 @@ static int dm_test_fastboot_mmc_part(struct unit_test_state *uts)
&part_info, response)); &part_info, response));
ut_asserteq(0, fastboot_mmc_get_part_info("0.0:0", &fb_dev_desc, ut_asserteq(0, fastboot_mmc_get_part_info("0.0:0", &fb_dev_desc,
&part_info, response)); &part_info, response));
ut_asserteq(0, fastboot_mmc_get_part_info("1", &fb_dev_desc, ut_asserteq(0, fastboot_mmc_get_part_info("2", &fb_dev_desc,
&part_info, response)); &part_info, response));
ut_asserteq(0, fastboot_mmc_get_part_info("1.0", &fb_dev_desc, ut_asserteq(0, fastboot_mmc_get_part_info("2.0", &fb_dev_desc,
&part_info, response)); &part_info, response));
ut_asserteq(1, fastboot_mmc_get_part_info(":1", &fb_dev_desc, ut_asserteq(1, fastboot_mmc_get_part_info(":1", &fb_dev_desc,
&part_info, response)); &part_info, response));