All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: linux-usb@vger.kernel.org
Subject: Re: USB hub problem
Date: Mon, 16 Aug 2021 22:25:01 +1000	[thread overview]
Message-ID: <426a1ad4-b0a5-3e26-b871-f5d987401f6f@eyal.emu.id.au> (raw)
In-Reply-To: <00311c3e-9b32-792d-8320-d6080bc9585c@suse.com>



On 16/08/2021 20.30, Oliver Neukum wrote:
> 
> On 15.08.21 01:32, Eyal Lebedinsky wrote:
>> I searched the hub model and IDs but did not find relevant information.
>> Is there an official list of supported hubs (or devices)?
> 
> No, any hub by implementing the hub specification is supported.
> 
>> Attaching the phone does not add a device.
> 
> Just for the sake of completeness, could you post 'lsusb -v'
> for that hub?

Bus 001 Device 095: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               2.10
   bDeviceClass            9 Hub
   bDeviceSubClass         0
   bDeviceProtocol         2 TT per port
   bMaxPacketSize0        64
   idVendor           0x0bda Realtek Semiconductor Corp.
   idProduct          0x5411 RTS5411 Hub
   bcdDevice            1.04
   iManufacturer           1 Generic
   iProduct                2 4-Port USB 2.0 Hub
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength       0x0029
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0xe0
       Self Powered
       Remote Wakeup
     MaxPower                0mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         9 Hub
       bInterfaceSubClass      0
       bInterfaceProtocol      1 Single TT
       iInterface              0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0001  1x 1 bytes
         bInterval              12
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       1
       bNumEndpoints           1
       bInterfaceClass         9 Hub
       bInterfaceSubClass      0
       bInterfaceProtocol      2 TT per port
       iInterface              0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0001  1x 1 bytes
         bInterval              12

>> ## plug phone:
>>          (no new messages)
> That suggests a bug in the hub firmware. specifically that
> under unknown circumstances it fails to generate events
> for connection changes.

I do not know it it is of value, but when the phone is not detected, it also does not
indicate that it is connected using MTP. It thinks it is only being charged only.

>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: new high-speed USB device
>> number 57 using xhci_hcd
>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device found,
>> idVendor=04e8, idProduct=6860, bcdDevice= 4.00
>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device strings: Mfr=2,
>> Product=3, SerialNumber=4
>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: Product: SAMSUNG_Android
> 
> In other respects it does work.
> 
> Based on a hunch, could you test whether the circumstances
> this device fails under is related to runtime PM?
> 
> In order to do so you boot with
> 
> usbcore.autosuspend=-1
 >
> 
> on the kernel command line.

Well I can do better. I use USB TV tuners and in /etc/modprobe.d/dvb.conf I see
	options usbcore autosuspend=-1
It is a leftover from using an old tuner.

>      Regards
>          Oliver

Thanks

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au)

      reply	other threads:[~2021-08-16 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 23:32 USB hub problem Eyal Lebedinsky
2021-08-15  6:28 ` Greg KH
2021-08-15  7:47   ` Eyal Lebedinsky
2021-08-15  8:54     ` Felipe Balbi
2021-08-15 10:35       ` Eyal Lebedinsky
2021-08-16 10:30 ` Oliver Neukum
2021-08-16 12:25   ` Eyal Lebedinsky [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=426a1ad4-b0a5-3e26-b871-f5d987401f6f@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --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 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.