From patchwork Wed Jan 22 14:17:36 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Flavio Suligoi X-Patchwork-Id: 239932 List-Id: U-Boot discussion From: f.suligoi at asem.it (Flavio Suligoi) Date: Wed, 22 Jan 2020 15:17:36 +0100 Subject: [PATCH] imx: distinguish POR from POR+WDOG reset cause for first wd Message-ID: <1579702656-20667-1-git-send-email-f.suligoi@asem.it> In some application the possibility to check if the reset is caused by a watchdog is essential, even if it occurs simultaneously with POR. Signed-off-by: Flavio Suligoi --- arch/arm/mach-imx/cpu.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-imx/cpu.c b/arch/arm/mach-imx/cpu.c index bfa85c6..ce0c663 100644 --- a/arch/arm/mach-imx/cpu.c +++ b/arch/arm/mach-imx/cpu.c @@ -47,7 +47,6 @@ static char *get_reset_cause(void) { switch (get_imx_reset_cause()) { case 0x00001: - case 0x00011: return "POR"; case 0x00004: return "CSU"; @@ -59,6 +58,12 @@ static char *get_reset_cause(void) #else return "WDOG"; #endif + case 0x00011: +#ifdef CONFIG_MX7 + return "POR + WDOG1"; +#else + return "POR + WDOG"; +#endif case 0x00020: return "JTAG HIGH-Z"; case 0x00040: