From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: eric.ernst@linux.intel.com
Cc: wim@iguana.be, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org,
Gabriel Touzeau <gabrielx.touzeau@intel.com>,
Yann Puech <yann.puech@intel.com>,
Jeremy Compostella <jeremy.compostella@intel.com>,
David Cohen <david.a.cohen@linux.intel.com>
Subject: Re: [PATCH 1/1] watchdog: Adding Merrifield watchdog driver support
Date: Fri, 3 Jan 2014 15:03:24 +0000 [thread overview]
Message-ID: <20140103150324.3f36cb50@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <1388710602-18513-1-git-send-email-eric.ernst@linux.intel.com>
On Thu, 2 Jan 2014 16:56:42 -0800
eric.ernst@linux.intel.com wrote:
> From: Gabriel Touzeau <gabrielx.touzeau@intel.com>
>
> Added Merrifield watchdog driver support.
>
> Based on initial implementation from prior Intel SCU-based platforms, this
> driver has several changes specific to the Tangier SoC / Merrifield platform.
We have a watchdog driver layer now. Any new driver should be using that.
It deals with a lot of the work for you so you'll just need the actual
methods doing the work. It also registers both the legacy device and new
style watchdog nodes as appropriate so you can have multiple watchdogs on
a system.
Look at watchdog_core.c and watchdog_dev.c and the various things that
use it.
Alan
next prev parent reply other threads:[~2014-01-03 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 0:56 [PATCH 1/1] watchdog: Adding Merrifield watchdog driver support eric.ernst
2014-01-03 7:54 ` Dmitry Torokhov
2014-01-03 15:03 ` One Thousand Gnomes [this message]
2014-01-04 5:44 ` Guenter Roeck
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=20140103150324.3f36cb50@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=david.a.cohen@linux.intel.com \
--cc=eric.ernst@linux.intel.com \
--cc=gabrielx.touzeau@intel.com \
--cc=jeremy.compostella@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
--cc=yann.puech@intel.com \
/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).