From: David Cohen <david.a.cohen@linux.intel.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: wim@iguana.be, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/2] x86: intel-mid: add watchdog platform code for Merrifield
Date: Wed, 9 Apr 2014 11:00:32 -0700 [thread overview]
Message-ID: <20140409180031.GA23460@psi-dev26.jf.intel.com> (raw)
In-Reply-To: <20140409134223.6444a598@alan.etchedpixels.co.uk>
On Wed, Apr 09, 2014 at 01:42:23PM +0100, One Thousand Gnomes wrote:
> On Tue, 8 Apr 2014 13:59:04 -0700
> David Cohen <david.a.cohen@linux.intel.com> wrote:
>
> > This patch adds platform code for Intel Merrifield.
> > Since the watchdog is not part of SFI table, we have no other option but
> > to manually register watchdog's platform device (argh!).
>
> Before going too far down that path have you considered compiling in a
> devicetree instead ?
This is the only device missing from SFI table I am aware of.
The original implementation is to register the watchdog without a
device/driver match. i.e. directly from the init call. Then the init
call has a conditional check if it's Merrifield with
intel_mid_identify_cpu() to avoid it being registered in !Merrifield
platforms. But I want to lock this intel_mid_identify_cpu() inside
intel_mid platform code, since it's too ugly to stay inside drivers.
If we figure out there's more devices missing from SFI table, then we
could revisit here and consider another approach.
Br, David
>
> Alan
next prev parent reply other threads:[~2014-04-09 18:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 20:59 [PATCH 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-08 20:59 ` [PATCH 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-08 23:56 ` Randy Dunlap
2014-04-09 17:48 ` David Cohen
2014-04-10 13:51 ` Guenter Roeck
2014-04-10 18:24 ` David Cohen
2014-04-09 0:17 ` Guenter Roeck
2014-04-09 12:41 ` One Thousand Gnomes
2014-04-08 20:59 ` [PATCH 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-09 12:42 ` One Thousand Gnomes
2014-04-09 13:49 ` Alexander Stein
2014-04-09 13:58 ` One Thousand Gnomes
2014-04-09 14:03 ` Alexander Stein
2014-04-09 15:18 ` Guenter Roeck
2014-04-09 16:10 ` Alexander Stein
2014-04-09 17:15 ` Guenter Roeck
2014-04-10 11:08 ` One Thousand Gnomes
2014-04-09 18:00 ` David Cohen [this message]
2014-04-10 19:15 ` Guenter Roeck
2014-04-10 19:30 ` David Cohen
2014-04-10 20:35 ` Guenter Roeck
2014-04-10 21:23 ` David Cohen
2014-04-10 22:51 ` Guenter Roeck
2014-04-11 20:50 ` [PATCH v2 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-11 20:50 ` [PATCH v2 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-11 20:50 ` [PATCH v2 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-15 18:41 ` [PATCH v3 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-15 18:41 ` [PATCH v3 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-15 19:01 ` Guenter Roeck
2014-04-15 19:24 ` David Cohen
2014-04-15 18:41 ` [PATCH v3 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-15 19:09 ` Guenter Roeck
2014-04-15 19:30 ` David Cohen
2014-04-15 20:06 ` [PATCH v4 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-15 20:06 ` [PATCH v4 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-16 0:13 ` Guenter Roeck
2014-04-15 20:06 ` [PATCH v4 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-15 20:09 ` David Cohen
2014-04-15 21:13 ` Guenter Roeck
2014-04-15 21:17 ` David Cohen
2014-04-15 21:35 ` Guenter Roeck
2014-04-15 21:39 ` David Cohen
2014-04-15 22:20 ` [PATCH v4.1 " David Cohen
2014-04-16 0:16 ` 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=20140409180031.GA23460@psi-dev26.jf.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=wim@iguana.be \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).