From: Greg KH <gregkh@linuxfoundation.org>
To: Akshay Gujar <Akshay.Gujar@harman.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
naveen.v@harman.com, oneukum@suse.com, stern@rowland.harvard.edu
Subject: Re: [PATCH v5 2/3] Documentation: ABI: document DEVICE_ENUMERATION_FAILURE uevent
Date: Fri, 17 Jul 2026 12:37:32 +0200 [thread overview]
Message-ID: <2026071745-ambulance-reload-4e29@gregkh> (raw)
In-Reply-To: <20260715114028.3627807-3-Akshay.Gujar@harman.com>
On Wed, Jul 15, 2026 at 11:40:27AM +0000, Akshay Gujar wrote:
> Document the DEVICE_ENUMERATION_FAILURE environment variable emitted
> in KOBJ_CHANGE uevents when device enumeration fails.
>
> Signed-off-by: Akshay Gujar <Akshay.Gujar@harman.com>
> ---
> Documentation/ABI/testing/sysfs-uevent | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-uevent b/Documentation/ABI/testing/sysfs-uevent
> index 0b6227706b35e..e362c34aa2ef6 100644
> --- a/Documentation/ABI/testing/sysfs-uevent
> +++ b/Documentation/ABI/testing/sysfs-uevent
> @@ -49,3 +49,28 @@ Description:
>
> Users:
> udev, userspace tools generating synthetic uevents
> +
> +What: DEVICE_ENUMERATION_FAILURE
> +Date: July 2026
> +KernelVersion: 7.3
> +Description:
> + Some devices may be detected but fail to enumerate
> + due to protocol-level errors or invalid responses.
> +
> + A KOBJ_CHANGE uevent includes the following environment
> + variable when this occurs:
> +
> + DEVICE_ENUMERATION_FAILURE=<dev_name>
> +
> + The value is the kernel device name of the device for
> + which enumeration failed, as returned by dev_name().
> +
> + Example (USB):
> +
> + ACTION=change
> + SUBSYSTEM=usb
> + DEVTYPE=usb_interface
This will be the port device, not the usb interface, right?
> + DEVICE_ENUMERATION_FAILURE=usb1-port1
That looks right.
> +
> +Users:
> + udev, userspace tools monitoring device enumeration failures
> \ No newline at end of file
Didn't checkpatch complain about this?
And is there actually udev code to handle this being proposed anywhere?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-17 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:40 [PATCH v5 0/3] driver core: add enumeration failure uevent helper Akshay Gujar
2026-07-15 11:40 ` [PATCH v5 1/3] driver core: add device_enumeration_failure_notify() helper Akshay Gujar
2026-07-17 10:40 ` Greg KH
2026-07-15 11:40 ` [PATCH v5 2/3] Documentation: ABI: document DEVICE_ENUMERATION_FAILURE uevent Akshay Gujar
2026-07-17 10:37 ` Greg KH [this message]
2026-07-15 11:40 ` [PATCH v5 3/3] usb: hub: send enumeration failure uevent Akshay Gujar
2026-07-17 10:35 ` [PATCH v5 0/3] driver core: add enumeration failure uevent helper Greg KH
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=2026071745-ambulance-reload-4e29@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Akshay.Gujar@harman.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=naveen.v@harman.com \
--cc=oneukum@suse.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