f989711a60
Some devices may belong to >1 power domain, so with the current design this is something not possible to describe. It's worth to note that Linux also uses the `power-domains` naming scheme, not `power-domain`. This patch also introduces `power-domain-names` so that each entry in `power-domains` can be given a name if needed. `#power-domain-cells` is now required as well. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
38 lines
712 B
Plaintext
38 lines
712 B
Plaintext
/*
|
|
* Copyright (c) 2021 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
/ {
|
|
test_domain: test_domain {
|
|
compatible = "power-domain";
|
|
status = "okay";
|
|
#power-domain-cells = <0>;
|
|
};
|
|
|
|
test_dev_a: test_dev_a {
|
|
compatible = "test-device-pm";
|
|
status = "okay";
|
|
power-domains = <&test_domain>;
|
|
};
|
|
|
|
test_dev_b: test_dev_b {
|
|
compatible = "test-device-pm";
|
|
status = "okay";
|
|
power-domains = <&test_domain>;
|
|
};
|
|
|
|
test_domain_balanced: test_domain_balanced {
|
|
compatible = "power-domain";
|
|
status = "okay";
|
|
#power-domain-cells = <0>;
|
|
};
|
|
|
|
test_dev_balanced: test_dev_balanced {
|
|
compatible = "test-device-pm";
|
|
status = "okay";
|
|
power-domains = <&test_domain_balanced>;
|
|
};
|
|
};
|