summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
diff options
context:
space:
mode:
authorMarco Felsch <m.felsch@pengutronix.de>2020-02-27 12:06:04 +0100
committerShawn Guo <shawnguo@kernel.org>2020-03-11 15:36:16 +0800
commit1f4e29d24b9da9854456cd3c517a8cf6bd2bfd67 (patch)
tree24da31e35f3667e98ce1686d9ba41d98974b0a3a /arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
parent684720000af86ae04191c3a88bf07b972f7f4a4c (diff)
ARM: dts: imx6: phycore-som: explicit disable pmic watchdog during suspend
By default the phycore-som has support for two watchdog devices: 1st the internal imx6 watchdog and 2nd the DA9062 PMIC watchdog. According [1] the PMIC watchdog is used as boot watchdog. It is common to use this watchdog during "system up" time too. Furthermore the PMIC watchdog can be used to address ERR007117 since the phycore-som can be equipped with NAND or eMMC storage. The PMIC watchdog can be enabled/disabled by the PMIC itself if the PMIC enters POWERDOWN mode or by the host. The PMIC powerdown mode can't be used due to the PCB design. So the watchdog is still enabled during a suspend which causes a system reset. We need to tell the driver to disable the watchdog during a system suspend and to reenable it upon a resume to fix this. [1] https://git.pengutronix.de/cgit/barebox/tree/arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi#n73 Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Diffstat (limited to 'arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi')
-rw-r--r--arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
index 978dc1c2ff1b..356fe5673be9 100644
--- a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
@@ -107,6 +107,7 @@
watchdog {
compatible = "dlg,da9062-watchdog";
+ dlg,use-sw-pm;
};
regulators {