From: "Seth Heasley (Linux)" <seth.heasley@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Seth Heasley <seth.heasley@intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH v1] i2c: ismt: Add support for Intel Emmitsburg PCH
Date: Mon, 14 Sep 2020 02:43:56 -0700 [thread overview]
Message-ID: <b11640ffc0956412c1cab112d881f569f5e7dd9a.camel@linux.intel.com> (raw)
In-Reply-To: <20200615161001.12817-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
Sorry for the slow response.
> Add PCI ID for the Intel Emmitsburg PCH iSMT SMBus controller.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Seth Heasley <seth.heasley@linux.intel.com>
> ---
> drivers/i2c/busses/i2c-ismt.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-ismt.c b/drivers/i2c/busses/i2c-
> ismt.c
> index 2f95e25a10f7..cdba77f9ecb1 100644
> --- a/drivers/i2c/busses/i2c-ismt.c
> +++ b/drivers/i2c/busses/i2c-ismt.c
> @@ -77,6 +77,7 @@
> #define PCI_DEVICE_ID_INTEL_S1200_SMT1 0x0c5a
> #define PCI_DEVICE_ID_INTEL_CDF_SMT 0x18ac
> #define PCI_DEVICE_ID_INTEL_DNV_SMT 0x19ac
> +#define PCI_DEVICE_ID_INTEL_EBG_SMT 0x1bff
> #define PCI_DEVICE_ID_INTEL_AVOTON_SMT 0x1f15
>
> #define ISMT_DESC_ENTRIES 2 /* number of descriptor entries */
> @@ -184,6 +185,7 @@ static const struct pci_device_id ismt_ids[] = {
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_INTEL_S1200_SMT1) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_CDF_SMT)
> },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_DNV_SMT)
> },
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_EBG_SMT)
> },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_INTEL_AVOTON_SMT) },
> { 0, }
> };
-Seth
next prev parent reply other threads:[~2020-09-14 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 16:10 [PATCH v1] i2c: ismt: Add support for Intel Emmitsburg PCH Andy Shevchenko
2020-08-05 9:39 ` Wolfram Sang
2020-08-28 15:02 ` Andy Shevchenko
2020-09-21 10:03 ` Wolfram Sang
2020-09-14 9:43 ` Seth Heasley (Linux) [this message]
2020-09-21 10:05 ` Wolfram Sang
2020-09-21 10:00 ` Wolfram Sang
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=b11640ffc0956412c1cab112d881f569f5e7dd9a.camel@linux.intel.com \
--to=seth.heasley@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=seth.heasley@intel.com \
--cc=wsa@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).