
Hi Claudius,
On Thu, Nov 28, 2019 at 9:07 AM Claudius Heine ch@denx.de wrote:
Signed-off-by: Claudius Heine ch@denx.de
arch/arm/dts/imx6qdl-dhcom-pdk2.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/arch/arm/dts/imx6qdl-dhcom-pdk2.dtsi b/arch/arm/dts/imx6qdl-dhcom-pdk2.dtsi index af4719aaeb..572bcbf8f0 100644 --- a/arch/arm/dts/imx6qdl-dhcom-pdk2.dtsi +++ b/arch/arm/dts/imx6qdl-dhcom-pdk2.dtsi @@ -30,6 +30,11 @@ mux-int-port = <1>; mux-ext-port = <3>; };
wdt-reboot {
compatible = "wdt-reboot";
wdt = <&wdog1>;
};
};
Could you use the the same way that Linux handles the imx2_wdt?
Please see the commit below:
commit ceea0c145d0c38badfcfc5443138e94ab094dc4a Author: Robert Hancock hancock@sedsystems.ca Date: Tue Aug 6 11:05:29 2019 -0600
watchdog: imx: Add DT ext-reset handling
The Linux imx2_wdt driver uses a fsl,ext-reset-output boolean in the device tree to specify whether the board design should use the external reset instead of the internal reset. Use this boolean to determine which mode to use rather than using external reset unconditionally.
For the legacy non-DM mode, the external reset is always used in order to maintain the previous behavior.
Signed-off-by: Robert Hancock hancock@sedsystems.ca