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>
52 lines
1.2 KiB
Plaintext
52 lines
1.2 KiB
Plaintext
/ {
|
|
test_reg: test_reg {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 0 0>;
|
|
#power-domain-cells = <0>;
|
|
};
|
|
|
|
test_reg_chained: test_reg_chained {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 1 0>;
|
|
power-domains = <&test_reg>;
|
|
#power-domain-cells = <0>;
|
|
};
|
|
|
|
test_reg_chained_auto: test_reg_chained_auto {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 2 0>;
|
|
power-domains = <&test_reg>;
|
|
#power-domain-cells = <0>;
|
|
zephyr,pm-device-runtime-auto;
|
|
};
|
|
|
|
test_reg_auto: test_reg_auto {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 3 0>;
|
|
#power-domain-cells = <0>;
|
|
zephyr,pm-device-runtime-auto;
|
|
};
|
|
|
|
test_reg_auto_chained: test_reg_auto_chained {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 4 0>;
|
|
#power-domain-cells = <0>;
|
|
power-domains = <&test_reg_auto>;
|
|
};
|
|
|
|
test_reg_auto_chained_auto: test_reg_auto_chained_auto {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 5 0>;
|
|
power-domains = <&test_reg_auto>;
|
|
#power-domain-cells = <0>;
|
|
zephyr,pm-device-runtime-auto;
|
|
};
|
|
|
|
test_reg_disabled: test_reg_disabled {
|
|
compatible = "power-domain-gpio";
|
|
enable-gpios = <&gpio0 6 0>;
|
|
#power-domain-cells = <0>;
|
|
status = "disabled";
|
|
};
|
|
};
|