From: Samuel Ortiz <sameo@linux.intel.com>
To: Seth Heasley <seth.heasley@intel.com>
Cc: linux-kernel@vger.kernel.org, James Ralston <james.d.ralston@intel.com>
Subject: Re: [PATCH 1/1] lpc_sch: Add Intel Centerton Multifunction Device support
Date: Mon, 16 Apr 2012 18:21:02 +0200 [thread overview]
Message-ID: <20120416162102.GM24130@sortiz-mobl> (raw)
In-Reply-To: <1332349191-8068-1-git-send-email-seth.heasley@intel.com>
Hi Seth,
On Wed, Mar 21, 2012 at 09:59:51AM -0700, Seth Heasley wrote:
> This patch adds the DeviceIDs for the Intel Centerton Legacy Block. The Legacy Block includes SMBus, GPIO, and Watchdog functionality.
>
> Signed-off-by: Seth Heasley <seth.heasley@intel.com>
> ---
> drivers/mfd/lpc_sch.c | 16 +++++++++++++---
> 1 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mfd/lpc_sch.c b/drivers/mfd/lpc_sch.c
> index abc4213..778af13 100644
> --- a/drivers/mfd/lpc_sch.c
> +++ b/drivers/mfd/lpc_sch.c
> @@ -36,10 +36,13 @@
>
> #define GPIOBASE 0x44
> #define GPIO_IO_SIZE 64
> +#define GPIO_IO_SIZE_128 128
>
> #define WDTBASE 0x84
> #define WDT_IO_SIZE 64
>
> +#define PCI_DEVICE_ID_INTEL_CENTERTON_ILB 0x0c60
> +
So we're not going to need this ID anywhere else ? In the GPIO driver for
example ?
If we do need it there, this ID should move to pci_ids.h
> static struct resource smbus_sch_resource = {
> .flags = IORESOURCE_IO,
> };
> @@ -68,7 +71,7 @@ static struct resource wdt_sch_resource = {
>
> static struct mfd_cell tunnelcreek_cells[] = {
> {
> - .name = "tunnelcreek_wdt",
> + .name = "ie6xx_wdt",
What do we need this change for ?
The rest of the patch looks good.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-04-16 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 16:59 Seth Heasley
2012-04-16 16:21 ` Samuel Ortiz [this message]
2012-04-16 16:42 ` Heasley, Seth
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=20120416162102.GM24130@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=james.d.ralston@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@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
Powered by JetHome