This is what I get from acpidump:
marcusmae@m1k:~$ sudo acpidump | grep OTDG
marcusmae@m1k:~$ sudo acpidump | grep XDCI
1AA0: 5F 41 44 52 0C 00 00 15 00 5B 82 0F 58 44 43 49 _ADR.....[..XDCI
3160: 42 38 58 44 43 49 14 1A 5F 50 4C 44 00 A4 5E 5E B8XDCI.._PLD..^^
31B0: A0 0E 90 50 4D 45 45 60 86 58 44 43 49 0A 02 5B ...PMEE`.XDCI..[
3200: 44 44 4E 0D 42 72 6F 78 74 6F 6E 20 58 44 43 49 DDN.Broxton XDCI
B170: 00 5C 2F 04 5F 53 42 5F 50 43 49 30 58 44 43 49 .\/._SB_PCI0XDCI
Does this look sufficient?
Kind regards,
- Dmitry.
пт, 23 окт. 2020 г. в 12:09, Felipe Balbi <balbi@xxxxxxxxxx>:
>
> Heikki Krogerus <heikki.krogerus@xxxxxxxxxxxxxxx> 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
