From: James Clark <jjc@jclark.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Cc: Johan Hovold <johan@kernel.org>,
Bastien Nocera <hadess@hadess.net>,
Matthias Kaehlcke <mka@chromium.org>,
Arnd Bergmann <arnd@arndb.de>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Douglas Anderson <dianders@chromium.org>,
Robert Nelson <robertcnelson@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, regressions@lists.linux.dev
Subject: [PATCH v4 0/2] usb: misc: onboard_usb_dev: don't defer probing after the device is configured
Date: Fri, 6 Nov 2026 13:12:49 +0700 [thread overview]
Message-ID: <cover.1793941292.git.jjc@jclark.com> (raw)
On a BeagleY-AI, kernels since commit f918e3804498 ("arm64: enable
HAVE_SHARED_GPIOS for all ARM64 platforms") no longer boot: the on-board
USB hub is re-probed in a loop, because onboard_usb_dev defers probing
after the hub has been configured.
v3 added a pre_probe callback to the USB core, which turned out to add
significant complexity. v4 follows Johan Hovold's other suggestion [1]
instead. Patch 1 exports the generic driver's operations. Patch 2
changes onboard_usb_dev to call them itself instead of setting
generic_subclass.
Tested on the BeagleY-AI on top of v7.4-rc1: the board boots normally,
and unbinding and rebinding the onboard-usb-dev platform device works.
I used an LLM coding assistant to help prepare this series.
[1] https://lore.kernel.org/all/auSdA8MfolA8OhdM@hovoldconsulting.com/
v3: https://lore.kernel.org/all/cover.1793669297.git.jjc@jclark.com/
v2: https://lore.kernel.org/all/20261030151919.3511106-1-jjc@jclark.com/
v1: https://lore.kernel.org/all/20261030114705.3159093-1-jjc@jclark.com/
James Clark (2):
usb: core: export the generic device driver's operations
usb: misc: onboard_usb_dev: don't defer probing after the device is
configured
drivers/usb/core/generic.c | 4 ++++
drivers/usb/core/usb.h | 6 ------
drivers/usb/misc/onboard_usb_dev.c | 14 +++++++++++---
include/linux/usb.h | 10 +++++++++-
4 files changed, 24 insertions(+), 10 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.56.0
next reply other threads:[~2026-11-06 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 6:12 James Clark [this message]
2026-11-06 6:12 ` [PATCH v4 1/2] usb: core: export the generic device driver's operations James Clark
2026-11-06 17:02 ` Alan Stern
2026-11-06 6:12 ` [PATCH v4 2/2] usb: misc: onboard_usb_dev: don't defer probing after the device is configured James Clark
2026-11-06 6:35 ` sashiko-bot
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=cover.1793941292.git.jjc@jclark.com \
--to=jjc@jclark.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=johan@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=regressions@lists.linux.dev \
--cc=robertcnelson@gmail.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