All of lore.kernel.org
 help / color / mirror / Atom feed
From: zumeng.chen@windriver.com (Zumeng Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Watchdog: OMAP: Fix the runtime pm code to avoid module getting stuck intransition state.
Date: Mon, 9 Jul 2012 09:16:34 +0800	[thread overview]
Message-ID: <4FFA30F2.7010909@windriver.com> (raw)
In-Reply-To: <20120708092612.GA735@spo001.leaseweb.com>

? 2012?07?08? 17:26, Wim Van Sebroeck ??:
> Hi All,
>
>> Hello, Lokesh,
>>
>> One question: Does "echo 1>  /dev/watchdog" work well?
>>
>> Regards,
>> Zumeng
> Please note hat "echo 1>  /dev/watchdog" for drivers that have the WDIOF_MAGICCLOSE
> flag set, reboots the system. This is because it opens the watchdog device ; then
> writes the characters "1" to it and then closes the watchdog. So the watchdog keeps
> running (because it didn't see the magic char "V" written to it).
Yes, this is _absolutely_ right.
>
> In this case (omap_wdt) it opens the watchdog device (and starts the watchdog) then
> it writes a "1" to the watchdog (so basically the watchdog is being pinged) and then
> closes the watchdog device (which stops the watchdog if NOWAYOUT was not set).
Wim,

Agreed for all above, sorry for jumping in:

I just have a little question about this patch:


we have enable pm_runtime_enable(wdev->dev) in probe,
and do ret = misc_register(&(wdev->omap_wdt_miscdev));

Then this patch wants to remove pm_runtime_get_sync
in file operation function, is that right?

Regards,
Zumeng

>
> Kind regards,
> Wim.
>

  parent reply	other threads:[~2012-07-09  1:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  5:23 [PATCH] Watchdog: OMAP: Fix the runtime pm code to avoid module getting stuck intransition state Lokesh Vutla
2012-06-18  5:41 ` Shilimkar, Santosh
2012-06-18  5:41   ` Shilimkar, Santosh
2012-06-30  7:23   ` Vutla, Lokesh
2012-06-30  7:23     ` Vutla, Lokesh
2012-07-02  5:19   ` Vutla, Lokesh
2012-07-02  5:19     ` Vutla, Lokesh
2012-07-04 16:02   ` Shilimkar, Santosh
2012-07-04 16:02     ` Shilimkar, Santosh
2012-07-07 12:27     ` Wim Van Sebroeck
2012-07-07 12:28       ` Shilimkar, Santosh
2012-07-07 12:28         ` Shilimkar, Santosh
2012-07-05 14:36 ` Bedia, Vaibhav
2012-07-06  7:21   ` Shilimkar, Santosh
2012-07-06  7:21     ` Shilimkar, Santosh
2012-07-06  7:21     ` Shilimkar, Santosh
2012-07-06 12:29     ` Bedia, Vaibhav
2012-07-06 12:29       ` Bedia, Vaibhav
2012-07-06 12:29       ` Bedia, Vaibhav
2012-07-08  7:49 ` Zumeng Chen
     [not found]   ` <20120708092612.GA735@spo001.leaseweb.com>
2012-07-09  1:16     ` Zumeng Chen [this message]
2012-07-09  3:49       ` Vutla, Lokesh

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=4FFA30F2.7010909@windriver.com \
    --to=zumeng.chen@windriver.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.