From: Jean Delvare <khali@linux-fr.org>
To: james.d.ralston@intel.com
Cc: Ben Dooks <ben-linux@fluff.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Rob Landley <rob@landley.net>,
Seth Heasley <seth.heasley@intel.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Ralf Baechle <ralf@linux-mips.org>,
Manuel Lauss <manuel.lauss@googlemail.com>,
Olof Johansson <olof@lixom.net>,
linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] i2c-i801: Add Device IDs for Intel Lynx Point-LP PCH
Date: Wed, 29 Aug 2012 19:54:52 +0200 [thread overview]
Message-ID: <20120829195452.4fa8ebaa@endymion.delvare> (raw)
In-Reply-To: <1344530632-2645-1-git-send-email-james.d.ralston@intel.com>
Hi James,
Quite a long Cc list for such a trivial patch...
On Thu, 9 Aug 2012 09:43:52 -0700, james.d.ralston@intel.com wrote:
> From: James Ralston <james.d.ralston@intel.com>
>
> This patch adds the SMBus Device IDs for the Intel Lynx Point-LP PCH. The Device IDs are defined in drivers/i2c/busses/i2c-i801.c
I'm curious what the "LP" stands for. Low power?
>
> Signed-off-by: James Ralston <james.d.ralston@intel.com>
> ---
> Documentation/i2c/busses/i2c-i801 | 1 +
> drivers/i2c/busses/Kconfig | 1 +
> drivers/i2c/busses/i2c-i801.c | 3 +++
> 3 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/i2c/busses/i2c-i801 b/Documentation/i2c/busses/i2c-i801
> index 615142d..53207df 100644
> --- a/Documentation/i2c/busses/i2c-i801
> +++ b/Documentation/i2c/busses/i2c-i801
> @@ -21,6 +21,7 @@ Supported adapters:
> * Intel DH89xxCC (PCH)
> * Intel Panther Point (PCH)
> * Intel Lynx Point (PCH)
> + * Intel Lynx Point_LP (PCH)
You spelled it "Lynx Point-LP" (with dash not underscore) in the patch
summary. Consistency in naming would be preferred. I'll use a dash
everywhere and apply your patch.
> Datasheets: Publicly available at the Intel website
>
> On Intel Patsburg and later chipsets, both the normal host SMBus controller
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index 2e7530a..3500af7 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -104,6 +104,7 @@ config I2C_I801
> DH89xxCC (PCH)
> Panther Point (PCH)
> Lynx Point (PCH)
> + Lynx Point_LP (PCH)
>
> This driver can also be built as a module. If so, the module
> will be called i2c-i801.
> diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
> index 898dcf9..c467038 100644
> --- a/drivers/i2c/busses/i2c-i801.c
> +++ b/drivers/i2c/busses/i2c-i801.c
> @@ -52,6 +52,7 @@
> DH89xxCC (PCH) 0x2330 32 hard yes yes yes
> Panther Point (PCH) 0x1e22 32 hard yes yes yes
> Lynx Point (PCH) 0x8c22 32 hard yes yes yes
> + Lynx Point_LP (PCH) 0x9c22 32 hard yes yes yes
>
> Features supported by this driver:
> Software PEC no
> @@ -155,6 +156,7 @@
> #define PCI_DEVICE_ID_INTEL_DH89XXCC_SMBUS 0x2330
> #define PCI_DEVICE_ID_INTEL_5_3400_SERIES_SMBUS 0x3b30
> #define PCI_DEVICE_ID_INTEL_LYNXPOINT_SMBUS 0x8c22
> +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS 0x9c22
>
> struct i801_priv {
> struct i2c_adapter adapter;
> @@ -771,6 +773,7 @@ static DEFINE_PCI_DEVICE_TABLE(i801_ids) = {
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_DH89XXCC_SMBUS) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_PANTHERPOINT_SMBUS) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_LYNXPOINT_SMBUS) },
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS) },
> { 0, }
> };
>
--
Jean Delvare
prev parent reply other threads:[~2012-08-29 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 16:43 [PATCH 4/5] i2c-i801: Add Device IDs for Intel Lynx Point-LP PCH james.d.ralston
2012-08-29 17:54 ` Jean Delvare [this message]
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=20120829195452.4fa8ebaa@endymion.delvare \
--to=khali@linux-fr.org \
--cc=ben-linux@fluff.org \
--cc=djkurtz@chromium.org \
--cc=james.d.ralston@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@googlemail.com \
--cc=olof@lixom.net \
--cc=ralf@linux-mips.org \
--cc=rob@landley.net \
--cc=seth.heasley@intel.com \
--cc=w.sang@pengutronix.de \
/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).