diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2019-09-09 06:00:03 -0700 |
|---|---|---|
| committer | Jagan Teki <jagan@amarulasolutions.com> | 2020-01-27 22:27:21 +0530 |
| commit | bfcd9298b29c16fdada9d8e772dd9aaff7760f43 (patch) | |
| tree | 4b0289ac68d0b18af3ab672bbbb346a67495b618 /test | |
| parent | 7bacce524d48594dae399f9ee9280ab105f6c8cf (diff) | |
test: dm: spi: Fix sandbox dm_test_spi_find()
Per sandbox_cs_info(), sandbox spi controller only supports chip
select 0. Current test case tries to locate devices on chip select
1, and any call to spi_get_bus_and_cs() or spi_cs_info() with cs
number 1 should not return 0.
This updates the test case to handle it correctly.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Jagan Teki <jagan@amarulasolutions.com>
Diffstat (limited to 'test')
| -rw-r--r-- | test/dm/spi.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/test/dm/spi.c b/test/dm/spi.c index ffd789cd7f..8e417acc5f 100644 --- a/test/dm/spi.c +++ b/test/dm/spi.c @@ -77,10 +77,10 @@ static int dm_test_spi_find(struct unit_test_state *uts) /* We should be able to add something to another chip select */ ut_assertok(sandbox_sf_bind_emul(state, busnum, cs_b, bus, node, "name")); - ut_assertok(spi_get_bus_and_cs(busnum, cs_b, speed, mode, + ut_asserteq(-EINVAL, spi_get_bus_and_cs(busnum, cs_b, speed, mode, "spi_flash_std", "name", &bus, &slave)); - ut_assertok(spi_cs_info(bus, cs_b, &info)); - ut_asserteq_ptr(info.dev, slave->dev); + ut_asserteq(-EINVAL, spi_cs_info(bus, cs_b, &info)); + ut_asserteq_ptr(NULL, info.dev); /* * Since we are about to destroy all devices, we must tell sandbox |