From: Felipe Balbi <balbi@kernel.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"Dmitry N. Mikushin" <maemarcus@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Any example of USB gadget for DRD device mode on Intel Gemini Lake?
Date: Fri, 23 Oct 2020 13:08:59 +0300 [thread overview]
Message-ID: <87lffxdzk4.fsf@kernel.org> (raw)
In-Reply-To: <20201023064855.GR1667571@kuha.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Heikki Krogerus <heikki.krogerus@linux.intel.com> writes:
> On Thu, Oct 22, 2020 at 11:06:59PM +0200, Dmitry N. Mikushin wrote:
>> Yes, AFAIK PCI_DEVICE_ID_INTEL_GLK_XHCI is actually 0x31a8, and I do have it:
>>
>> 00:15.0 USB controller [0c03]: Intel Corporation Device [8086:31a8] (rev 03)
>
> That is the xHCI controller, and it is not what you need if you want
> to use the connector in device mode. The xHCI and DWC3 IPs are
> separate IPs on GLK. That is why there is a mux between the two. The
> dwc3 USB device controller has device ID 31aa, so you want to see a
> PCI device with the device ID. It's not there.
>
> So the dwc3 PCI device is not enabled on your board, which means you
> do not have USB device controller to deal with. The connector is in
> host mode only. Sorry.
>
> If you can enter the BIOS menu, then you can try to find an option
> named XDCI (so that's "XDCI" not "xHCI"). It is usually somewhere
> under some USB menu. If you have that, then enable it, and you should
> see the dwc3 PCI device in the operating system.
Also, have a look at acpidump. See if the device even exists in your
DSDT but, perhaps, disabled (look at the _STA method for OTDG or XDCI)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2020-10-23 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 11:27 Any example of USB gadget for DRD device mode on Intel Gemini Lake? Dmitry N. Mikushin
2020-10-19 13:36 ` Heikki Krogerus
2020-10-22 21:06 ` Dmitry N. Mikushin
2020-10-22 21:25 ` Sid Spry
2020-10-22 21:51 ` Dmitry N. Mikushin
2020-10-22 23:04 ` Sid Spry
2020-10-22 23:47 ` Dmitry N. Mikushin
2020-10-23 6:48 ` Heikki Krogerus
2020-10-23 10:08 ` Felipe Balbi [this message]
2020-10-23 22:34 ` Dmitry N. Mikushin
2020-10-26 7:11 ` Felipe Balbi
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=87lffxdzk4.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=maemarcus@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).