Linux USB
 help / color / mirror / Atom feed
From: "Diederik de Haas" <diederik@cknow-tech.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Huacai Chen" <chenhuacai@loongson.cn>
Cc: "Huacai Chen" <chenhuacai@kernel.org>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>, "Shengwen Xiao" <atzlinux@sina.com>,
	<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH] USB: OHCI/UHCI: Add soft dependencies on ehci_hcd
Date: Tue, 30 Dec 2025 15:40:27 +0100	[thread overview]
Message-ID: <DFBMNYF0U5PK.24YOAUZFZ0ESB@cknow-tech.com> (raw)
In-Reply-To: <2025123049-cadillac-straggler-d2fb@gregkh>

On Tue Dec 30, 2025 at 9:15 AM CET, Greg Kroah-Hartman wrote:
> On Tue, Dec 30, 2025 at 04:00:14PM +0800, Huacai Chen wrote:
>> Commit 9beeee6584b9aa4f ("USB: EHCI: log a warning if ehci-hcd is not
>> loaded first") said that ehci-hcd should be loaded before ohci-hcd and
>> uhci-hcd. However, commit 05c92da0c52494ca ("usb: ohci/uhci - add soft
>> dependencies on ehci_pci") only makes ohci-pci/uhci-pci depend on ehci-
>> pci, which is not enough and we may still see the warnings in boot log.
>> So fix it by also making ohci-hcd/uhci-hcd depend on ehci-hcd.
>> 
>> Cc: stable@vger.kernel.org
>> Reported-by: Shengwen Xiao <atzlinux@sina.com>
>> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
>> ---
>>  drivers/usb/host/ohci-hcd.c | 1 +
>>  drivers/usb/host/uhci-hcd.c | 1 +
>>  2 files changed, 2 insertions(+)
>> 
>> diff --git a/drivers/usb/host/ohci-hcd.c b/drivers/usb/host/ohci-hcd.c
>> index 9c7f3008646e..549c965b7fbe 100644
>> --- a/drivers/usb/host/ohci-hcd.c
>> +++ b/drivers/usb/host/ohci-hcd.c
>> @@ -1355,4 +1355,5 @@ static void __exit ohci_hcd_mod_exit(void)
>>  	clear_bit(USB_OHCI_LOADED, &usb_hcds_loaded);
>>  }
>>  module_exit(ohci_hcd_mod_exit);
>> +MODULE_SOFTDEP("pre: ehci_hcd");
>
> Ick, no, this way lies madness.  I hate the "softdep" stuff, it's
> usually a sign that something is wrong elsewhere.
>
> And don't add this _just_ to fix a warning message in a boot log, if you
> don't like that message, then build the module into your kernel, right?
>
> And I really should just go revert 05c92da0c524 ("usb: ohci/uhci - add
> soft dependencies on ehci_pci") as well, that feels wrong too.

FWIW, I've been seeing this warning on several of my Rockchip based
devices as well. I thought I had already mentioned that on some ML, but
couldn't find it on lore.k.o ... turns out I reported it on my 'own' ML:
https://lists.sr.ht/~diederik/pine64-discuss/%3CDD65LB64HB7K.15ZYRTB98X8G2@cknow.org%3E
(and likely on #linux-rockchip IRC channel)

Most of it is just my research notes, but the last post also had this:

```
I checked the last 20 boots on my devices to see that warning (or not).
Device				Number of times that warning showed up
Rock64 (rk3328)			16x
RockPro64 (rk3399)		11x
Quartz64 Model A (rk3566)	 7x
Quartz64 Model B (rk3566)	14x
PineTab2 (rk3566)		17x
NanoPi R5S (rk3568)		13x
Rock 5B (rk3588)		12x
```

While I generally don't like seeing warning messages, it often also
resulted in USB2 ports not working. Maybe even every time, but I only
notice it when I actually tried to use one of the USB2 ports.

The first post mentioned what I 'assume' to be the problem:
```
CONFIG_USB_XHCI_HCD=m
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
```

So I guess USB_EHCI_HCD doesn't work with '=m'.

Cheers,
  Diederik

  parent reply	other threads:[~2025-12-30 14:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  8:00 [PATCH] USB: OHCI/UHCI: Add soft dependencies on ehci_hcd Huacai Chen
2025-12-30  8:15 ` Greg Kroah-Hartman
2025-12-30  9:00   ` xiao sheng wen(肖盛文)
2025-12-30 14:40   ` Diederik de Haas [this message]
2025-12-30 16:42     ` Alan Stern
2025-12-31  9:38       ` Huacai Chen
2025-12-31 15:20         ` Alan Stern
2026-01-02  2:36           ` Huacai Chen
2026-01-02 15:13             ` Alan Stern
2026-01-03  3:16               ` Huacai Chen
2026-01-03  3:33                 ` Alan Stern
2026-01-03  3:57                   ` Huacai Chen
2026-01-03 16:41                     ` Alan Stern
2026-01-10  4:05                       ` Huacai Chen
2026-01-10 15:00                         ` Alan Stern
2026-01-11  1:54                           ` Huacai Chen
2026-01-11  2:04                             ` Alan Stern
2025-12-31 17:33       ` Diederik de Haas
2025-12-31 18:09         ` Alan Stern
2025-12-30 16:23   ` Alan Stern

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=DFBMNYF0U5PK.24YOAUZFZ0ESB@cknow-tech.com \
    --to=diederik@cknow-tech.com \
    --cc=atzlinux@sina.com \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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