voidWatchdogAVR::disable() {// Disable the watchdog and clear any saved watchdog timer value.wdt_disable(); _wdto =-1; } 开发者ID:AcriCAA,项目名称:Adafruit_SleepyDog,代码行数:5,代码来源:WatchdogAVR.cpp 示例6: main ▲点赞 1▼ intmain(){wdt_disable();// no watchdog, just becaus...
--- a/drivers/watchdog/twl4030_wdt.c +++ b/drivers/watchdog/twl4030_wdt.c @@ -190,6 +190,8 @@ static int __devinit twl4030_wdt_probe(struct platform_device *pdev) twl4030_wdt_dev = pdev; + twl4030_wdt_disable(wdt); + ret = misc_register(&wdt->miscdev); if (ret) { d...
> +++ b/drivers/watchdog/twl4030_wdt.c > @@ -190,6 +190,8 @@ static int __devinit twl4030_wdt_probe(struct > platform_device *pdev) > > twl4030_wdt_dev = pdev; > > + twl4030_wdt_disable(wdt); > + > ret = misc_register(&wdt->miscdev); > if (ret) { > dev_err(...
> not have the watchdog enabled. Maybe we should disable the watchdog only > in case the registration actually fails? > > And even in that case, do we want to disable the watchdog? What are the > situations where watchdog registration can fail? Is there a possibility > that we would...
Thanks for the detailed explanation. I was worried about the kernel and the early user space booting being in the "grey area" where errors might occurr which can cause the device (I'm talking about embedded devices here) to go into failed state without watchdog being able to reboot the ...