SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 5/5] watchdog: sh_mobile: add driver
Date: Mon, 02 Feb 2015 10:09:59 +0000	[thread overview]
Message-ID: <1741717.r8MbnsiXNB@avalon> (raw)
In-Reply-To: <1422802074-1921-6-git-send-email-wsa@the-dreams.de>

Hi Geert,

On Monday 02 February 2015 11:01:54 Geert Uytterhoeven wrote:
> On Mon, Feb 2, 2015 at 10:54 AM, Laurent Pinchart wrote:
> > How about PM (system and runtime) support ? How does the watchdog behave
> > during system suspend ? You could then replace the clk_prepare_enable()
> > and
> > clk_disable_unprepare() calls with pm_runtime_get_sync() and
> > pm_runtime_put().
>
> That's a good question.
> 
> If the RWDT MSTP clock is disabled, it can't count, and thus can't trigger.

I'd still like to test that. MSTP stands for module stop. While this is 
probably implemented as clock gates in most cases, there is no guarantee that 
it will always be the case. All MSTP guarantees is that the module is stopped, 
but the definition of "stopped" isn't explained. The watchdog counter might 
behave in a special way.

> But I don't know what's the maximum time interval you can have in the system
> between enabling the MSTP clock during system resume, and the first call of
> watchdog_ops.sh_wdt_ping.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2015-02-02 10:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 14:47 [RFC 5/5] watchdog: sh_mobile: add driver Wolfram Sang
2015-02-02  0:28 ` Simon Horman
2015-02-02  1:02 ` Wolfram Sang
2015-02-02  1:54 ` Simon Horman
2015-02-02  9:54 ` Laurent Pinchart
2015-02-02 10:01 ` Geert Uytterhoeven
2015-02-02 10:06 ` Wolfram Sang
2015-02-02 10:09 ` Laurent Pinchart [this message]
2015-02-02 11:25 ` Wolfram Sang
2015-02-02 13:24 ` Wolfram Sang
2015-02-03  8:52 ` Laurent Pinchart
2015-02-03  9:09 ` Wolfram Sang

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=1741717.r8MbnsiXNB@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox