linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Loïc Yhuel" <loic.yhuel@gmail.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: No SuperSpeedPlus on ASM2142
Date: Mon, 16 Sep 2019 17:19:30 +0200	[thread overview]
Message-ID: <CANMwUkj5kyxE21fDutTyPnW9vibpYwG_602YFO6tB=Mkr8905w@mail.gmail.com> (raw)
In-Reply-To: <38c06b3b-d9b3-a175-9fb9-7d13f0501490@linux.intel.com>

Le lun. 16 sept. 2019 à 14:57, Mathias Nyman
<mathias.nyman@linux.intel.com> a écrit :
> So both places that indicate USB 3.1 support are not according to latest spec,
> SBRN (Serial Bus Release Number) is 30 instead of 31, and supported protocol
> capability minor revision is 0x1 instead of 0x10.
Yes. I searched for firmwares, but I only saw a much older version
available on Internet.

> Most reliable way of checking the current actual port speed is reading protocol speed id
> from the ports PORTSC register port-speed field.
> Use debugfs: (with your correct pci address and port number)
Currently I have "PortSpeed:4" which matches with the "Gen 1" trace.
If I even get a "Gen 2" trace again, I will check.

> Is the xHCI controller id PCI D0 state even when runtime suspeded?
> Some ACPI tables end up preventing D3 for runtime suspend, keeping controller in D0
> and possibly preventing PME# wake signaling
It seems you are right, lspci still shows D0 :
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-

The other USB controllers (AMD 3.0 and 3.1) have
"PME(D0+,D1-,D2-,D3hot+,D3cold+)",
are in D3 state when runtime suspended, and wake up correctly.

Looking at this, I realized the front panel USB3.0 connectors are on the AMD 3.1
controller, I wonder how they are limited to SuperSpeed (configured by
the BIOS ?).

  reply	other threads:[~2019-09-16 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16  2:41 No SuperSpeedPlus on ASM2142 Loïc Yhuel
2019-09-16 12:59 ` Mathias Nyman
2019-09-16 15:19   ` Loïc Yhuel [this message]
2019-09-16 20:53     ` Loïc Yhuel
2019-09-24  7:57       ` Mathias Nyman
2019-09-24 15:50         ` Loïc Yhuel
2019-10-07 23:37           ` ASM2142 issues Loïc Yhuel

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='CANMwUkj5kyxE21fDutTyPnW9vibpYwG_602YFO6tB=Mkr8905w@mail.gmail.com' \
    --to=loic.yhuel@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.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;
as well as URLs for NNTP newsgroup(s).