From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] watchdog/imx_watchdog: do not set WCR_WDW
Date: Wed, 25 Mar 2015 14:08:07 +0100 [thread overview]
Message-ID: <5512B337.3050209@denx.de> (raw)
In-Reply-To: <20150325121524.GB30752@linutronix.de>
Hi Sebastian,
On 25/03/2015 13:15, Sebastian Andrzej Siewior wrote:
>>
>> Just some questions. The described behavior is coherent with the
>> description in the manual. When WDW is set, the watchdog is stopped
>> while the processor is in wait mode.
>
> I fail to notice how it could make any sense.
Well, I have not said it makes sense - only that the behavior is
expected ;-)
>
>> Current imx2_wdt.c driver in kernel does not care about this bit, but it
>> looks like that only the kernel and/or the application can decide if the
>> watchdog should run when the system is in WAIT or not. The bootloader
>> cannot decide, and it should set the bit for its own usage.
>>
>> Should this setup be done by the kernel driver instead of by the
>> bootloader ?
>
> It is a one-time-bit. Once it is set (or not) it can not be changed
> later. It makes no difference for the bootloader.
mmhhh..Sorry, it looks like I read the wrong line in the manual. This is
a write once bit exactly as WDZST. My assumption were wrong. We cannot
disable in kernel if the bootloader has already activated it.
> And the kernel may
> remain idle for longer than one jiffy with NO_HZ but it will still wake
> up within a second if I remember correctly. Eitherway the user will
> usually trigger the WD in timeout/2 so atleast that timer will wake up
> the kernel from idle.
> Having the WDT not account the idle time makes it hard for the user to
> figure out how much time has been accounted by the WDT so far.
I have no objections here - I start from the wrong assumption that the
bit could be cleared by the kernel, but it is not.
>
>>>
>>> While I don't see a reason why the WDT should not be running while the
>>> CPU is in idle, I'm dropping this bit.
>>
>> I can agree or disagree. This depends on the application.
>>
>> Differently as the WDZST, that can be set only once, and it is set by
>> *both* U-Boot and kernel (setting in kernel has then no influence), the
>> WDW can be even disabled in kernel.
>
> I patched the kernel as well. Once I get through here I would also push
> patches there. The thing I don't like is that the kernel pings the WDT
> on its own. While it may make sense for some people I would like to
> atleast configure it :)
Agree, patch put in my merge queue.
Acked-by: Stefano Babic <sbabic@denx.de>
Best regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2015-03-25 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:45 [U-Boot] [PATCH] watchdog/imx_watchdog: do not set WCR_WDW Sebastian Andrzej Siewior
2015-03-25 8:03 ` Stefano Babic
2015-03-25 12:15 ` Sebastian Andrzej Siewior
2015-03-25 13:08 ` Stefano Babic [this message]
2015-03-25 15:53 ` Stefano Babic
2015-03-26 8:02 ` Sebastian Andrzej Siewior
2015-03-26 8:27 ` Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5512B337.3050209@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox