From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
James Ralston
<james.d.ralston-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] i2c-i801: Add device ID for Intel Wildcat Point PCH
Date: Wed, 16 Jul 2014 19:42:04 +0200 [thread overview]
Message-ID: <20140716174204.GH2759@katana> (raw)
In-Reply-To: <20140629210054.6a51c91f-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3235 bytes --]
On Sun, Jun 29, 2014 at 09:00:54PM +0200, Jean Delvare wrote:
> Signed-off-by: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>
> Cc: James Ralston <james.d.ralston-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
I will likely take this patch, nonetheless an Ack from someone from
Intel would be much appreciated.
> ---
> Untested, but the datasheet show full compatibility with previous
> chipsets.
>
> Documentation/i2c/busses/i2c-i801 | 1 +
> drivers/i2c/busses/Kconfig | 1 +
> drivers/i2c/busses/i2c-i801.c | 3 +++
> 3 files changed, 5 insertions(+)
>
> --- linux-3.16-rc2.orig/Documentation/i2c/busses/i2c-i801 2014-06-16 05:45:28.000000000 +0200
> +++ linux-3.16-rc2/Documentation/i2c/busses/i2c-i801 2014-06-29 20:49:27.079679858 +0200
> @@ -25,6 +25,7 @@ Supported adapters:
> * Intel Avoton (SOC)
> * Intel Wellsburg (PCH)
> * Intel Coleto Creek (PCH)
> + * Intel Wildcat Point (PCH)
> * Intel Wildcat Point-LP (PCH)
> * Intel BayTrail (SOC)
> Datasheets: Publicly available at the Intel website
> --- linux-3.16-rc2.orig/drivers/i2c/busses/Kconfig 2014-06-23 10:45:34.372425164 +0200
> +++ linux-3.16-rc2/drivers/i2c/busses/Kconfig 2014-06-29 20:48:02.904000652 +0200
> @@ -109,6 +109,7 @@ config I2C_I801
> Avoton (SOC)
> Wellsburg (PCH)
> Coleto Creek (PCH)
> + Wildcat Point (PCH)
> Wildcat Point-LP (PCH)
> BayTrail (SOC)
>
> --- linux-3.16-rc2.orig/drivers/i2c/busses/i2c-i801.c 2014-06-25 18:19:11.531786078 +0200
> +++ linux-3.16-rc2/drivers/i2c/busses/i2c-i801.c 2014-06-29 20:49:14.062420369 +0200
> @@ -59,6 +59,7 @@
> * Wellsburg (PCH) MS 0x8d7e 32 hard yes yes yes
> * Wellsburg (PCH) MS 0x8d7f 32 hard yes yes yes
> * Coleto Creek (PCH) 0x23b0 32 hard yes yes yes
> + * Wildcat Point (PCH) 0x8ca2 32 hard yes yes yes
> * Wildcat Point-LP (PCH) 0x9ca2 32 hard yes yes yes
> * BayTrail (SOC) 0x0f12 32 hard yes yes yes
> *
> @@ -175,6 +176,7 @@
> #define PCI_DEVICE_ID_INTEL_COLETOCREEK_SMBUS 0x23b0
> #define PCI_DEVICE_ID_INTEL_5_3400_SERIES_SMBUS 0x3b30
> #define PCI_DEVICE_ID_INTEL_LYNXPOINT_SMBUS 0x8c22
> +#define PCI_DEVICE_ID_INTEL_WILDCATPOINT_SMBUS 0x8ca2
> #define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS 0x8d22
> #define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS0 0x8d7d
> #define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1 0x8d7e
> @@ -823,6 +825,7 @@ static const struct pci_device_id i801_i
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS2) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_COLETOCREEK_SMBUS) },
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_SMBUS) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS) },
> { 0, }
>
>
> --
> Jean Delvare
> SUSE L3 Support
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-07-16 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 19:00 [PATCH] i2c-i801: Add device ID for Intel Wildcat Point PCH Jean Delvare
[not found] ` <20140629210054.6a51c91f-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-07-16 17:42 ` Wolfram Sang [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=20140716174204.GH2759@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=james.d.ralston-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jdelvare-l3A5Bk7waGM@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).