All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "James Clark" <jjc@jclark.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v5 2/2] usb: misc: onboard_usb_dev: don't defer probing after the device is configured
Date: Sat, 07 Nov 2026 02:54:16 +0000	[thread overview]
Message-ID: <sashiko-outbox-202518@kernel.org> (raw)
In-Reply-To: <e0e60a57c500ffbdb6addc268d41b7dcc4cf6c4a.1794018128.git.jjc@jclark.com>

> onboard_usb_dev breaks the rule that a driver must not return
> -EPROBE_DEFER from its probe after it has registered child devices (see
> commit fbc35b45f9f6 ("Add documentation on meaning of -EPROBE_DEFER")).
> Its USB device driver sets generic_subclass, so the generic probe runs
> first and registers the device's interfaces. onboard_dev_usbdev_probe()
> then returns -EPROBE_DEFER until the platform device for the onboard
> device has probed. On the BeagleY-AI, this results in a probe loop,
> which has broken booting since commit f918e3804498 ("arm64: enable
> HAVE_SHARED_GPIOS for all ARM64 platforms").
> 
> Call the generic driver's operations from the driver itself instead of
> relying on generic_subclass, so that the probe is deferred before the
> device is configured. The device now stays unconfigured while the probe
> is deferred, including when the platform device never probes. Before, it
> was configured and unconfigured repeatedly until the platform device
> probed.
> 
> Make onboard_dev_usbdev_match() not match a device when neither its
> node nor its peer hub's node has a platform device, so that the generic
> driver binds it instead. If the platform device goes away between match
> and probe, return -ENODEV instead of -EINVAL, so that usb_probe_device()
> falls back to the generic driver.
> 
> Fixes: 8bc063641ceb ("usb: misc: Add onboard_usb_hub driver")
> Suggested-by: Johan Hovold <johan@kernel.org>
> Signed-off-by: James Clark <jjc@jclark.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794018128.git.jjc@jclark.com?part=2


      reply	other threads:[~2026-11-07  2:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  2:36 [PATCH v5 0/2] usb: misc: onboard_usb_dev: don't defer probing after the device is configured James Clark
2026-11-07  2:36 ` [PATCH v5 1/2] usb: core: export the generic device driver's operations James Clark
2026-11-07  2:52   ` sashiko-bot
2026-11-07  2:36 ` [PATCH v5 2/2] usb: misc: onboard_usb_dev: don't defer probing after the device is configured James Clark
2026-11-07  2:54   ` sashiko-bot [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=sashiko-outbox-202518@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=jjc@jclark.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.