From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Minas Harutyunyan <hminas@synopsys.com>
Cc: Matt Corallo <oc2udbzfd@mattcorallo.com>,
linux-usb@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux.amoon@gmail.com
Subject: Re: ODROID-C1/-C2 USB Detection only triggered by some devices
Date: Tue, 29 Jun 2021 18:30:08 +0200 [thread overview]
Message-ID: <CAFBinCDsGtQaPLhMAb+A6DBihWzQiU409i2oer_ud5yQBvfM5w@mail.gmail.com> (raw)
In-Reply-To: <20210629161807.GB703497@rowland.harvard.edu>
Hi Alan,
On Tue, Jun 29, 2021 at 6:18 PM Alan Stern <stern@rowland.harvard.edu> wrote:
[...]
> > > usbcore.autosuspend=-1
> > wow, this helps indeed
> > my steps are:
> > - power off my Odroid-C1+
> > - unplug all USB devices
> > - boot with usbcore.autosuspend=-1 in the kernel cmdline
> > - plugin my Corsair Voyager USB 3.0 flash drive (which was only
> > detected before if an additional USB 2.0 flash drive was plugged in
> > during boot)
> > -> without any lsusb magic the device was immediately recognized
>
> That does show pretty convincingly that runtime suspend is causing the
> problem. But I still have no idea why the problem affects some devices
> and not others. It's a mystery.
Maybe because there's two related problems (I am guessing here):
The first issue is that USB hotplug is not working at all on my
Odroid-C1+ (which means: dwc2 + GL852G USB hub).
The second issue is that the workaround we had before (running lsusb
-vv to make "hot plugged" devices show up) is not working for some USB
devices.
It seems that using a different workaround (usbcore.autosuspend=-1)
makes *all* USB devices show up - even without any "lsusb -vv" call.
So I think we should focus on the first issue as it may also fix the
other problem as well.
[...]
> > after rebooting without usbcore.autosuspend=-1 (and no USB device
> > plugged in during boot):
> > # grep "" /sys/bus/usb/devices/*/power/autosuspend
> > /sys/bus/usb/devices/1-1/power/autosuspend:0
> > /sys/bus/usb/devices/usb1/power/autosuspend:0
> >
> > I think the next step is narrowing down which component is causing this issue.
>
> Maybe Minas can help. He knows a lot more about dwc2 than I do (which
> is practically nothing).
I'll wait for Minas then
> > Interestingly my PC (running 5.12.13-arch1-2) also has two Genesys
> > Logic USB hubs with the same USB vendor and device IDs as my
> > Odroid-C1+: 05e3:0610.
> > These hubs are connected to my AMD Ryzen 5000 CPU or the B550 chipset:
> > usb1 1d6b:0002 09 1IF [USB 2.00, 480 Mbps, 0mA]
> > (xhci-hcd 0000:02:00.0) hub
> > 1-3 05e3:0610 09 1IF [USB 2.10, 480 Mbps, 100mA]
> > (GenesysLogic USB2.0 Hub) hub
> > [...]
> > 1-7 05e3:0610 09 1IF [USB 2.00, 480 Mbps, 100mA]
> > (Genesys Logic, Inc. Hub) hub
> >
> > So far I have not observed any problems on my PC.
>
> Presumably because it uses xHCI rather than dwc2.
indeed. I think it's good to know that it's not an issue affecting all
Genesys Logic USB 2.0 hubs.
As you mentioned above it's most likely that dwc2 is the culprit here.
Or it might be some interoperability issue between dwc2 and GL852G
Best regards,
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-06-29 16:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 0:32 ODROID-C1/-C2 USB Detection only triggered by some devices Matt Corallo
2021-06-28 0:58 ` Alan Stern
2021-06-28 1:05 ` Matt Corallo
2021-06-28 1:16 ` Alan Stern
2021-06-28 1:24 ` Matt Corallo
2021-06-28 14:24 ` Alan Stern
2021-06-28 18:37 ` Martin Blumenstingl
2021-06-29 15:05 ` Alan Stern
2021-06-29 15:51 ` Martin Blumenstingl
2021-06-29 16:18 ` Alan Stern
2021-06-29 16:30 ` Martin Blumenstingl [this message]
2021-06-30 0:35 ` Alan Stern
2021-07-01 10:03 ` Anand Moon
2021-07-01 21:18 ` Martin Blumenstingl
2021-07-02 19:11 ` Anand Moon
2021-07-02 19:33 ` Martin Blumenstingl
[not found] ` <CANAwSgQH6HgFQ+xz15AoKhGUF9G18P-cHOVL2FvS_34FrW=bzQ@mail.gmail.com>
2021-07-13 15:41 ` Martin Blumenstingl
2021-06-30 23:09 ` Martin Blumenstingl
2021-07-10 17:07 ` Martin Blumenstingl
2021-07-11 8:15 ` ODROID-C1/-C2 USB Detection only triggered by some devices dwc2 Minas Harutyunyan
2021-07-11 17:56 ` Martin Blumenstingl
2021-07-12 6:42 ` Minas Harutyunyan
2021-07-12 11:35 ` Martin Blumenstingl
2021-07-14 15:27 ` Minas Harutyunyan
2021-07-14 23:16 ` Martin Blumenstingl
2021-07-15 1:44 ` Alan Stern
2021-07-15 2:04 ` Alan Stern
2021-07-18 21:24 ` Martin Blumenstingl
2021-07-19 14:53 ` Alan Stern
2021-07-19 15:03 ` Alan Stern
2021-07-20 21:55 ` Martin Blumenstingl
2021-07-21 15:58 ` Alan Stern
2021-08-03 20:20 ` Martin Blumenstingl
2021-08-03 21:32 ` Alan Stern
2021-12-12 16:08 ` Martin Blumenstingl
2022-01-10 22:05 ` Martin Blumenstingl
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=CAFBinCDsGtQaPLhMAb+A6DBihWzQiU409i2oer_ud5yQBvfM5w@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=hminas@synopsys.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=oc2udbzfd@mattcorallo.com \
--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 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).