All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James <bjlockie@lockie.ca>, linux-usb <linux-usb@vger.kernel.org>
Subject: Re: problem with USB-C
Date: Thu, 13 Jan 2022 09:40:05 +0100	[thread overview]
Message-ID: <Yd/lZVRPgcLUqTrn@kroah.com> (raw)
In-Reply-To: <Yd72gTFL0BsC7vtR@rowland.harvard.edu>

On Wed, Jan 12, 2022 at 10:40:49AM -0500, Alan Stern wrote:
> > >     |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
> > > 1.5M
> > >         ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
> > >     |__ Port 5: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid,
> > > 1.5M
> > >         ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
> > >     |__ Port 6: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid,
> > > 1.5M
> > >         ID 30fa:0400
> > > 
> > > 
> > > Why are the hubs listed as Linux Foundation 3.0 root hubs and not 3.1 root
> > > hubs?
> > 
> > Because your devices do not advertise themselves as a USB 3.1 root hub.
> > Perhaps the documentation is incorrect?
> 
> No, that's not it at all.
> 
> The reason why the root hubs for buses 2 and 4 above are both listed as 
> "Linux Foundation 3.0 root hub" is because in hcd.c, the 
> usb31_rh_dev_descriptor and usb3_rh_dev_descriptor structures both set 
> their idProduct values to 0x03, 0x00 (0x0003 in little-endian form).  
> Therefore the hardware database can't distinguish between them.

Ah, right, I totally missed that.  I saw the two different definitions,
but missed the device number.

> One possibility would be for the usb31_rh_dev_descriptor to use 0x04, 
> 0x00 (with the corresponding update to the udev hardware database).  
> Another possibility is for the hardware database entry for product 0x0003
> to be changed simply to "Linux Foundation USB-3 root hub", so that it 
> doesn't specify 3.0, 3.1, or 3.2.

I can do that.  Should only take a few years to trickle out to the
slower distros :)

thanks,

greg k-h

      parent reply	other threads:[~2022-01-13  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  0:56 problem with USB-C James
2022-01-12  7:02 ` Greg KH
2022-01-12 15:40   ` Alan Stern
2022-01-12 19:39     ` James
2022-01-13  8:40     ` Greg KH [this message]

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=Yd/lZVRPgcLUqTrn@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bjlockie@lockie.ca \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.