From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
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: Fri, 10 Jul 2026 15:01:51 +0200 [thread overview]
Message-ID: <2026071031-chasing-booted-ecc2@gregkh> (raw)
In-Reply-To: <20260615-usb-notify-not-enough-bandwidth-v1-1-09ee5098b42d@collabora.com>
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?
thanks,
greg k-h
prev parent reply other threads:[~2026-07-10 13:01 UTC|newest]
Thread overview: 2+ 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 [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=2026071031-chasing-booted-ecc2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nfraprado@collabora.com \
/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