From: shruthi.sanil@intel.com
To: balbi@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: heikki.krogerus@intel.com, srikanth.thokala@intel.com,
mallikarjunappa.sangannavar@intel.com, shruthi.sanil@intel.com
Subject: [PATCH 0/2] Update the PCIe device ID's for USB device controllers on Alder Lake platforms
Date: Tue, 13 Sep 2022 11:23:14 +0530 [thread overview]
Message-ID: <20220913055316.23050-1-shruthi.sanil@intel.com> (raw)
From: Shruthi Sanil <shruthi.sanil@intel.com>
Alder Lake has split die architecture for the USB device controllers.
The USB2 controller resides in the PCH sub system and the USB3 controller
resides in the CPU sub system. Hence we need to update both the device ID's
for the device to be enumerated correctly.
Shruthi Sanil (2):
usb: dwc3: pci: Update the macro names for USB PCIe device ID's for
Alder Lake platforms
usb: dwc3: pci: Add PCIe device ID for USB3 controller on CPU
sub-system for Alder Lake P
drivers/usb/dwc3/dwc3-pci.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
base-commit: e839a756012b6cad7a4eeb67b0598ac3f349f863
--
2.17.1
next reply other threads:[~2022-09-13 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 5:53 shruthi.sanil [this message]
2022-09-13 5:53 ` [PATCH 1/2] usb: dwc3: pci: Update the macro names for USB PCIe device ID's for " shruthi.sanil
2022-09-13 5:53 ` [PATCH 2/2] usb: dwc3: pci: Add PCIe device ID for USB3 controller on CPU sub-system for Alder Lake P shruthi.sanil
2022-09-22 5:58 ` [PATCH 0/2] Update the PCIe device ID's for USB device controllers on Alder Lake platforms Sanil, Shruthi
2022-09-22 6:53 ` gregkh
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=20220913055316.23050-1-shruthi.sanil@intel.com \
--to=shruthi.sanil@intel.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=srikanth.thokala@intel.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
all inboxes | Powered by JetHome®