topic Re: imx6d watchdog2 reboot fail and suspend issue in i.MX Processors

imx6d watchdog2 reboot fail and suspend issue

jiujinhong — Fri, 01 Dec 2017 06:19:59 GMT

Hi All,

1) the hardware didn't use WDOG_B and SW have removed WDOG_B in dts file, but when reboot, it still fail. So whats the best way to disable WDOG_B ? thanks.

        /* pinctrl_wdog: wdoggrp {
            fsl,pins = <
                MX6QDL_PAD_GPIO_1__WDOG2_B 0x80000000
            >;
        };*/

2) there are no LCD in hardware, so what is best way to disable android suspend after boot? the system qucikly enter into suspend even if reset screen_timeout in android framework.

BSP: android7.1.1, Linux4.1.15

Re: imx6d watchdog2 reboot fail and suspend issue

jiujinhong — Fri, 01 Dec 2017 07:20:46 GMT

1) suspend log

fec 2188000.ethernet eth0: no PHY, assuming direct connection to switch
libphy: PHY fixed-0:00 not found
fec 2188000.ethernet eth0: could not attach to PHY
init: Service 'bootanim' (pid 246) exited with status 0
PM: suspend entry 1970-01-01 00:00:42.872847003 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ...
PM: Wakeup pending, aborting suspend
last active wakeup source: eventpoll

Freezing of tasks aborted after 0.007 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:00:42.912851003 UTC
PM: suspend entry 1970-01-01 00:00:43.018032337 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.002 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
PM: suspend of devices complete after 221.328 msecs
PM: suspend devices took 0.220 seconds
PM: late suspend of devices complete after 1.205 msecs
PM: noirq suspend of devices complete after 1.217 msecs
Disabling non-boot CPUs ...
CPU1: shutdown
Resume caused by IRQ 51
Suspended for 0.000 seconds
Enabling non-boot CPUs ...
CPU1 is up
PM: noirq resume of devices complete after 1.655 msecs
PM: early resume of devices complete after 0.717 msecs
PM: resume of devices complete after 128.423 msecs
PM: resume devices took 0.130 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:01:28.177289333 UTC
PM: suspend entry 1970-01-01 00:01:28.630432333 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.002 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
PM: suspend of devices complete after 221.906 msecs
PM: suspend devices took 0.230 seconds
PM: late suspend of devices complete after 1.205 msecs
PM: noirq suspend of devices complete after 1.190 msecs
Disabling non-boot CPUs ...
CPU1: shutdown
Resume caused by IRQ 51
Suspended for 0.000 seconds
Enabling non-boot CPUs ...
CPU1 is up
PM: noirq resume of devices complete after 0.648 msecs
PM: early resume of devices complete after 0.677 msecs
PM: resume of devices complete after 129.519 msecs
PM: resume devices took 0.130 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:01:33.177543000 UTC
PM: suspend entry 1970-01-01 00:01:33.282336667 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.002 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Suspending console(s) (use no_console_suspend to debug)

2)watchdog2 issue seems fixed by slect fsl watchdog1 to reset in DTS gpc node

Re: imx6d watchdog2 reboot fail and suspend issue

jiujinhong — Fri, 01 Dec 2017 08:42:39 GMT

sabresd_6dq:/ # reboot
sysrq: SysRq : Emergency Remount R/O
EXT4-fs (mmcblk3p6): re-mounted. Opts: (null)
EXT4-fs (mmcblk3p4): re-mounted. Opts: (null)
Emergency Remount complete
imx2-wdt 20bc000.wdog: Device shutdown: Expect reboot!
reboot: Restarting system with command ''

still fail, seems randome

Re: imx6d watchdog2 reboot fail and suspend issue

igorpadykov — Fri, 01 Dec 2017 23:11:29 GMT

Hi jiu

reboot is performed writing to WDOGx_WCR register

so removing record in dts file may not help. Without WDOG_B

in hardware board may hang as processor may start in lower voltage

than necessary, since low power driver will decrease arm voltages.

So recommended to reset all board including pmic also.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: imx6d watchdog2 reboot fail and suspend issue

jiujinhong — Mon, 04 Dec 2017 02:31:05 GMT

Hi igor,

thanks. Whats " low power driver" meaningin this scenario? You mean to add "ldo_active_on" to fix this issue? the hardware actually use MMPF0100F0XXX PMIC driver(PMIC_STBY_REQ、PMIC_ON_REQ etc).

Re: imx6d watchdog2 reboot fail and suspend issue

igorpadykov — Mon, 04 Dec 2017 05:24:08 GMT

Hi jiu

rom expects arm voltage configured for operation 792 MHz, while

low power driver may lower arm core voltage (for example 0.925V&396 MHz).

Best regards
igor

Re: imx6d watchdog2 reboot fail and suspend issue

jiujinhong — Tue, 26 Dec 2017 10:04:02 GMT

Closed issue.

I have two hardware revision board, A can't reboot when in cpu low cpufreq. If increase cpufreq to 792+ Mhz,it can reboot. B can reboot even if cpu low cpufreq. I think the difference between them is HW IO assignment issue. If carefully fixed DTS issue, it should be fine.