All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Janusz Użycki" <j.uzycki@elproma.com.pl>
To: Guenter Roeck <linux@roeck-us.net>, linux-watchdog@vger.kernel.org
Cc: Wim Van Sebroeck <wim@iguana.be>
Subject: Re: watchdog: watchdog_dev: WATCHDOG_KEEP_ON feature
Date: Wed, 17 Sep 2014 13:09:22 +0200	[thread overview]
Message-ID: <54196BE2.2010800@elproma.com.pl> (raw)
In-Reply-To: <540D1F8F.2080802@roeck-us.net>

Hi Guenter.

W dniu 2014-09-08 05:16, Guenter Roeck pisze:
>
>>>> * I also added wdd->ops->ref/unref calls but I'm afraid that even 
>>>> original code is buggy in watchdog_dev.c. Is any driver that uses 
>>>> the pointers? In my opinion watchdog_open() should call 
>>>> wdd->ops->ref() before watchdog_start() and watchdog_release() 
>>>> should call wdd->ops->unref() before module_put(). Otherwise fault 
>>>> is possible if watchdog module is unloaded.
>>>> * I noticed that current watchdog core does not support 
>>>> suspend/resume case. If you want to use suspend without the patch 
>>>> you need to close a watchdog in userspace using the magic character 
>>>> before suspend command. With the patch you must to use 
>>>> WDIOC_SETOPTIONS ioctl and WDIOS_DISABLECARD/WDIOS_ENABLECARD. Is 
>>>> there any other method to suspend with watchdog?
>> Can kernel suspend a started (stoppable) watchdog? It dissapeared in 
>> 3.x. Now userland reaction seems to be required.
>>
> Really ? I see a number of watchdog drivers implementing it.
>

Three things about always active/running/enabled watchdogs:
- stop returns an error
- pm/suspend/resume are not supported
- if watchdog is running/active keep-on like feature should be enabled
- on register watchdog specific driver should check if watchdog was 
enabled before

Always active/running/enabled is related to watchdog attribute
and seems have direct influence on specific driver code.
Is there "never stop" software option needed for stoppable watchdogs?

Abore are just notes. Now I'm working under keep-on and stmp3xxx driver 
only.

best regards
Janusz

  parent reply	other threads:[~2014-09-17 11:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1751381AbaIDOwq/20140904145246Z+988@vger.kernel.org>
2014-09-04 15:47 ` watchdog: WatchDog Timer Driver Core: ping a hardware watchdog in kernel's space Janusz Użycki
2014-09-04 16:05   ` watchdog: WatchDog Timer Driver Core: ping a hardware watchdog in kernel's space [proposal] Janusz Użycki
2014-09-04 16:24     ` Janusz Użycki
2014-09-04 17:23       ` Fwd: " Janusz Użycki
2014-09-05  6:47         ` Janusz Użycki
2014-09-07 17:18   ` watchdog: WatchDog Timer Driver Core: ping a hardware watchdog in kernel's space Guenter Roeck
2014-09-08  1:14     ` watchdog: watchdog_dev: WATCHDOG_KEEP_ON feature Janusz Użycki
2014-09-08  1:18       ` Janusz Użycki
2014-09-08  3:24         ` Guenter Roeck
2014-09-08  3:16       ` Guenter Roeck
2014-09-08 12:14         ` Janusz Użycki
2014-09-10 17:24           ` Janusz Użycki
2014-09-11 10:47             ` Janusz Użycki
2014-09-17 11:09         ` Janusz Użycki [this message]
2014-09-18 11:07           ` watchdog's pm support preffered implementation Janusz Użycki
2014-09-18 21:40             ` Janusz Użycki
2014-09-18 22:02               ` Janusz Użycki
2014-09-19  3:11                 ` Guenter Roeck
2014-09-19  9:46                   ` Janusz Użycki
2014-09-19 11:23                     ` timers vs drivers suspend race Janusz Użycki
2014-09-19 13:44                       ` Janusz Użycki
2014-09-19 16:21                     ` watchdog's pm support preffered implementation Guenter Roeck
2014-09-23 12:07                       ` Janusz Użycki

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=54196BE2.2010800@elproma.com.pl \
    --to=j.uzycki@elproma.com.pl \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wim@iguana.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.