From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kernel@collabora.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: core: Notify through uevent when not enough bandwidth available
Date: Tue, 21 Jul 2026 10:14:23 -0300 [thread overview]
Message-ID: <309aef89f580ffc48f52c25846d050dcf04d01b0.camel@collabora.com> (raw)
In-Reply-To: <2026071031-chasing-booted-ecc2@gregkh>
On Fri, 2026-07-10 at 15:01 +0200, Greg Kroah-Hartman wrote:
> On Mon, Jun 15, 2026 at 10:35:33AM -0400, Nícolas F. R. A. Prado
> wrote:
> > Currently, when a new device is plugged in and the host controller
> > can't
> > find enough bandwidth for it, an error message is printed:
> >
> > usb 1-3: Not enough bandwidth for new device state.
> >
> > In order to allow userspace to react to this and suggest the user
> > to use
> > a different host controller, send a uevent with
> > 'USB_NOT_ENOUGH_BANDWIDTH=1' to the root hub device.
>
> Where is this new user/kernel api now documented? And what tool is
> going to be looking for it?
Sorry I missed that, I'll add the documentation at
Documentation/ABI/testing/usb-uevent in v2.
As for the user, Steam will use it.
--
Thanks,
Nícolas
prev parent reply other threads:[~2026-07-21 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 14:35 [PATCH] usb: core: Notify through uevent when not enough bandwidth available Nícolas F. R. A. Prado
2026-07-10 13:01 ` Greg Kroah-Hartman
2026-07-21 13:14 ` Nícolas F. R. A. Prado [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=309aef89f580ffc48f52c25846d050dcf04d01b0.camel@collabora.com \
--to=nfraprado@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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