linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters
Date: Wed, 14 Aug 2019 10:31:48 +0200	[thread overview]
Message-ID: <1565771508.25764.3.camel@suse.com> (raw)
In-Reply-To: <db0e8930ea94408ca7a38192ddfd203f@SVR-IES-MBX-03.mgc.mentorg.com>

Am Mittwoch, den 14.08.2019, 08:17 +0000 schrieb  Schmid, Carsten :
> [Resend - had mailer errors ]
> 
> Hi Florian,
> 
> today i have seen a strange behaviour of two D-Link DUB-1312 adapters (same Revision A1).
> Plugging them into the same port (!) on my device one of them is recognized as SuperSpeed, the other as high speed ???
> (working on 4.14.129 LTS)
> 
> From dmesg, the "faulty" one:
> [  530.585871] usb 1-2: new high-speed USB device number 4 using xhci_hcd   <<<<<<<<< HUH ????

XHCI is not like EHCI. It needs no companion controller, as it serves
all speeds.

> I had a look at the driver code of ax88179, but that one didn't change much in the past up to v5.2.
> Nothing that explains what i can see here.

This is on a lower layer than ax88179. This comes from xhci_hcd.
Is this a regression?

	Regards
		Oliver


  reply	other threads:[~2019-08-14  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14  8:17 Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters Schmid, Carsten
2019-08-14  8:31 ` Oliver Neukum [this message]
2019-08-14  8:56   ` AW: " Schmid, Carsten
2019-08-14 10:22     ` Schmid, Carsten
2019-08-14 13:07     ` Oliver Neukum
2019-08-15 12:02       ` AW: " Schmid, Carsten
2019-08-16 11:56         ` Schmid, Carsten
2019-08-19 12:11         ` Oliver Neukum
2019-08-19 12:27           ` AW: " Schmid, Carsten

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=1565771508.25764.3.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=Carsten_Schmid@mentor.com \
    --cc=f.fainelli@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).