From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org
Subject: Re: [PATCH] pwm: lpss: Add Intel Gemini Lake PCI ID
Date: Fri, 20 Jan 2017 12:25:33 +0200 [thread overview]
Message-ID: <1484907933.2133.266.camel@linux.intel.com> (raw)
In-Reply-To: <20170104154334.29046-1-mika.westerberg@linux.intel.com>
On Wed, 2017-01-04 at 18:43 +0300, Mika Westerberg wrote:
> Intel Gemini Lake PWM is pretty much same as used in Intel Broxton.
> Add
> this new PCI ID to the list of supported devices.
>
Since we didn't yet settle the dependence series, I will incorporate
your patch in the next version of that series.
Change looks good to me!
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> Hi, this is on top of Andy's series here:
>
> https://patchwork.ozlabs.org/patch/710104/
> https://patchwork.ozlabs.org/patch/710107/
> https://patchwork.ozlabs.org/patch/710105/
> https://patchwork.ozlabs.org/patch/710106/
>
> drivers/pwm/pwm-lpss-pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pwm/pwm-lpss-pci.c b/drivers/pwm/pwm-lpss-pci.c
> index dfe0a2e8e4de..2c2ca370dc26 100644
> --- a/drivers/pwm/pwm-lpss-pci.c
> +++ b/drivers/pwm/pwm-lpss-pci.c
> @@ -78,6 +78,7 @@ static const struct pci_device_id pwm_lpss_pci_ids[]
> = {
> { PCI_VDEVICE(INTEL, 0x1ac8), PWM_LPSS_BXT },
> { PCI_VDEVICE(INTEL, 0x2288), PWM_LPSS_BSW },
> { PCI_VDEVICE(INTEL, 0x2289), PWM_LPSS_BSW },
> + { PCI_VDEVICE(INTEL, 0x31c8), PWM_LPSS_BXT },
> { PCI_VDEVICE(INTEL, 0x5ac8), PWM_LPSS_BXT },
> { },
> };
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-01-20 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 15:43 [PATCH] pwm: lpss: Add Intel Gemini Lake PCI ID Mika Westerberg
2017-01-20 10:25 ` Andy Shevchenko [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=1484907933.2133.266.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).