From: Heiner Kallweit <hkallweit1@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>
Subject: Re: [PATCH] usb: core: improve handling of hubs with no ports
Date: Wed, 23 Feb 2022 21:58:56 +0100 [thread overview]
Message-ID: <131166ee-9926-2eb5-2abd-6bab294d2937@gmail.com> (raw)
In-Reply-To: <YhZB9C/xGaoslZzT@rowland.harvard.edu>
On 23.02.2022 15:17, Alan Stern wrote:
> On Wed, Feb 23, 2022 at 01:26:23PM +0100, Heiner Kallweit wrote:
>> On 23.02.2022 03:10, Alan Stern wrote:
>>> On Tue, Feb 22, 2022 at 10:13:09PM +0100, Heiner Kallweit wrote:
>>>>
>>>> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
>>>> index 83b5aff25..e3f40d1f4 100644
>>>> --- a/drivers/usb/core/hub.c
>>>> +++ b/drivers/usb/core/hub.c
>>>> @@ -1423,9 +1423,8 @@ static int hub_configure(struct usb_hub *hub,
>>>> ret = -ENODEV;
>>>> goto fail;
>>>> } else if (hub->descriptor->bNbrPorts == 0) {
>>>> - message = "hub doesn't have any ports!";
>>>> - ret = -ENODEV;
>>>> - goto fail;
>>>> + dev_info(hub_dev, "hub has no ports, exiting\n");
>>>> + return -ENODEV;
>>>> }
>>>>
>>>> /*
>>>
>>> How about instead changing xhci-hcd so that it doesn't try to register
>>> a USB-3 root hub if the controller doesn't have any USB-3 ports? I
>>> think that would make more sense.
>>>
>> Right, this would be better. I checked and it seems to be a little bit
>> bigger endeavor. If I let register_root_hub() fail, then this removes
>> the USB3 bus/host (shared hcd), but also the USB2 bus/host.
>> It took an additional change to xhci_plat_probe() to make it work on my
>> system. Not sure what the impact could be on systems not using
>> xhci_plat_probe(). Users may face the same issue like me, and having
>> a USB3 hub with no ports may remove also the USB2 bus/host.
>
> Don't change register_root_hub(). Just change xhci_plat_probe(); make
> it skip the second call to usb_add_hcd() if there are no USB-3 ports.
>
This works on my system. However a consequence is that xhci->shared_hcd
is NULL. There are a few places like the following in xhci.c where
this may result in a NPE. Not knowing the USB subsystem in detail
I can't say whether these places are in any relevant path.
static int xhci_run_finished(struct xhci_hcd *xhci)
{
if (xhci_start(xhci)) {
xhci_halt(xhci);
return -ENODEV;
}
xhci->shared_hcd->state = HC_STATE_RUNNING;
> Alan Stern
>
>> What I can do: submit my patches as RFC, then there's a better basis
>> for a discussion.
>>
>>> Alan Stern
>>
>> Heiner
Heiner
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-02-23 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 21:13 [PATCH] usb: core: improve handling of hubs with no ports Heiner Kallweit
2022-02-23 2:10 ` Alan Stern
2022-02-23 12:26 ` Heiner Kallweit
2022-02-23 14:17 ` Alan Stern
2022-02-23 14:58 ` Heiner Kallweit
2022-02-23 15:37 ` Alan Stern
2022-02-23 20:58 ` Heiner Kallweit [this message]
2022-02-23 22:13 ` Alan Stern
2022-02-24 20:06 ` Jack Pham
2022-02-24 20:16 ` Heiner Kallweit
2022-02-24 20:21 ` Alan Stern
2022-03-03 11:50 ` Mathias Nyman
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=131166ee-9926-2eb5-2abd-6bab294d2937@gmail.com \
--to=hkallweit1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-amlogic@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox