diff options
| author | Peng Fan | 2018-07-27 10:20:39 +0800 |
|---|---|---|
| committer | Anatolij Gustschin | 2018-08-06 11:52:19 +0200 |
| commit | 4624faadffdb1cad65ad0c77d5a302ccbfaf4eae (patch) | |
| tree | afbe276bc8272c2ee8d9160a378bfcc35bf933ca /test | |
| parent | 3ad3077848474d75f75cde31dc3eb80d075a4b82 (diff) | |
dm: power-domain: query power domain after get device
This is to test power_domain_on in device_probe.
If the device has a power-domain property, enable it
when probe the device. So add the test to check
whether it is powered on or not.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'test')
| -rw-r--r-- | test/dm/power-domain.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/test/dm/power-domain.c b/test/dm/power-domain.c index a1e1df2bb21..48318218a9e 100644 --- a/test/dm/power-domain.c +++ b/test/dm/power-domain.c @@ -26,6 +26,8 @@ static int dm_test_power_domain(struct unit_test_state *uts) ut_assertok(uclass_get_device_by_name(UCLASS_MISC, "power-domain-test", &dev_test)); + ut_asserteq(1, sandbox_power_domain_query(dev_power_domain, + TEST_POWER_DOMAIN)); ut_assertok(sandbox_power_domain_test_get(dev_test)); ut_assertok(sandbox_power_domain_test_on(dev_test)); |