linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: Query about vexpress_ct_ca9x4 watchdog issue ?
Date: Wed, 20 Apr 2011 10:07:03 +0530	[thread overview]
Message-ID: <4DAE62EF.7050508@st.com> (raw)
In-Reply-To: <1b4f89d.afd2.12f70a9e2b0.Coremail.bill_carson@126.com>

On 04/20/2011 07:37 AM, bill wrote:
> Hi viresh and arm guys:)
> 
> I am testing sp805 watchdog at vexpress board.
> 
> After open /dev/watchdog , I use WDIOC_GETTIMELEFT ioctl to get the time left for rebooting in a loop;
> while the timeleft is not decrementing, but stay as a constant 59s.
> 
> I read the WdogValue/WdogControl register as specified in SP805TRM, it does not change any way, 
> 
> WdogValue     --> 0xf0918000
> WdogControl   -->0x3
> 
> 
> It seems the value is correct, but watchdog is not triggered.
> I am really puzzled about this, can you give me some clue to find the root cause?
> 

Hi Bill,

It looks that you are also not getting WDT reset after specified timeout? Is it so?
So, probably driver is fine as it is tested on SPEAr.

Probably the issue might be with clock rate and clock enable. What is the clock rate
for wdt in your platform?
Driver calls clk_enable() and clk_get_rate(). Can you please verify that this is
working correctly.

-- 
viresh

  reply	other threads:[~2011-04-20  4:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  2:07 Query about vexpress_ct_ca9x4 watchdog issue ? bill
2011-04-20  4:37 ` viresh kumar [this message]
2011-04-20  6:46 ` bill
2011-04-20  7:16   ` viresh kumar
2011-04-20  7:27   ` bill
2011-04-20  8:09     ` viresh kumar
2011-04-20  8:22     ` bill
2011-04-20  8:27       ` viresh kumar
2011-04-20  8:33       ` bill

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=4DAE62EF.7050508@st.com \
    --to=viresh.kumar@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).