All of lore.kernel.org
 help / color / mirror / Atom feed
From: gdavis@mvista.com (George G. Davis)
To: linux-arm-kernel@lists.infradead.org
Subject: mpcore_wdt A9 questions
Date: Wed, 22 Sep 2010 11:56:34 -0400	[thread overview]
Message-ID: <20100922155634.GQ3555@mvista.com> (raw)
In-Reply-To: <99c9a321-49a1-42da-b49f-5cdd5c03e17a@SG2EHSMHS008.ehs.local>

Hello John,

On Wed, Sep 22, 2010 at 09:36:52AM -0600, John Linn wrote:
> Hi,
> 
> The A9 has a watchdog timer per CPU, but I don't see a way to use more
> than one watchdog timer (one for each CPU) using the mpcore_wdt driver.
> 
> I tried to do my research but maybe I missed something. Is this a
> limitation of watchdog timers in Linux or just this driver?

It's not strictly a limitation in the watchdog subsystem, I suspect
it just not something that anyone has needed thus far.  Anyway,
here's something I was working on for upstream which adds support
for all MPCore watchdog timers.  N.B. This is based on v2.6.34 give or
take, not sure if it applies to current.  It still has issues with
per-cpu interrupts but interrupts aren't currently used, so...

  reply	other threads:[~2010-09-22 15:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17  9:54 [PATCH] Watchdog: Adding support for Watchdog found with ARM CortexA9 Viresh KUMAR
2010-05-17  9:56 ` Viresh KUMAR
2010-05-17 10:44 ` Jassi Brar
2010-05-17 11:24   ` Viresh KUMAR
2010-05-18  9:25     ` srinidhi kasagar
2010-05-18 13:20       ` George G. Davis
2010-05-19  4:02         ` Viresh KUMAR
2010-05-19  5:17           ` srinidhi kasagar
2010-05-19  6:44             ` Viresh KUMAR
2010-09-22 15:36             ` mpcore_wdt A9 questions John Linn
2010-09-22 15:56               ` George G. Davis [this message]
2010-05-19  5:32           ` [PATCH] Watchdog: Adding support for Watchdog found with ARM CortexA9 Shilimkar, Santosh
2010-05-19  6:45             ` Viresh KUMAR

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=20100922155634.GQ3555@mvista.com \
    --to=gdavis@mvista.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.