From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: pci: add support for the Intel Alder Lake-S
Date: Tue, 6 Oct 2020 15:55:39 +0300 [thread overview]
Message-ID: <20201006125539.GA11595@kuha.fi.intel.com> (raw)
In-Reply-To: <20201006125152.55223-1-heikki.krogerus@linux.intel.com>
On Tue, Oct 06, 2020 at 03:51:52PM +0300, Heikki Krogerus wrote:
> This patch adds the necessary PCI ID for Intel Alder Lake-S
> devices.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/dwc3/dwc3-pci.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drivers/usb/dwc3/dwc3-pci.c
> index f5a61f57c74f0..42ed6bc4dab63 100644
> --- a/drivers/usb/dwc3/dwc3-pci.c
> +++ b/drivers/usb/dwc3/dwc3-pci.c
> @@ -40,6 +40,7 @@
> #define PCI_DEVICE_ID_INTEL_TGPLP 0xa0ee
> #define PCI_DEVICE_ID_INTEL_TGPH 0x43ee
> #define PCI_DEVICE_ID_INTEL_JSP 0x4dee
> +#define PCI_DEVICE_ID_INTEL_ADLS 0x7ae1
>
> #define PCI_INTEL_BXT_DSM_GUID "732b85d5-b7a7-4a1b-9ba0-4bbd00ffd511"
> #define PCI_INTEL_BXT_FUNC_PMU_PWR 4
> @@ -366,6 +367,9 @@ static const struct pci_device_id dwc3_pci_id_table[] = {
> { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_JSP),
> (kernel_ulong_t) &dwc3_pci_intel_properties, },
>
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_ADLS),
> + (kernel_ulong_t) &dwc3_pci_intel_swnode, },
> +
Oh, this is broken. I have to resend. Sorry about that.
thanks,
--
heikki
prev parent reply other threads:[~2020-10-06 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 12:51 [PATCH] usb: dwc3: pci: add support for the Intel Alder Lake-S Heikki Krogerus
2020-10-06 12:55 ` Heikki Krogerus [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=20201006125539.GA11595@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.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