Documentation/ABI/testing/usb-uevent

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/usb-uevent

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/usb-uevent
Extension: [no extension]
Size: 794 bytes
Lines: 28
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:		Raise a uevent when a USB Host Controller has died
Date:		2019-04-17
KernelVersion:	5.2
Contact:	linux-usb@vger.kernel.org
Description:	When the USB Host Controller has entered a state where it is no
		longer functional a uevent will be raised. The uevent will
		contain ACTION=offline and ERROR=DEAD.

		Here is an example taken using udevadm monitor -p::

		    KERNEL[130.428945] offline  /devices/pci0000:00/0000:00:10.0/usb2 (usb)
		    ACTION=offline
		    BUSNUM=002
		    DEVNAME=/dev/bus/usb/002/001
		    DEVNUM=001
		    DEVPATH=/devices/pci0000:00/0000:00:10.0/usb2
		    DEVTYPE=usb_device
		    DRIVER=usb
		    ERROR=DEAD
		    MAJOR=189
		    MINOR=128
		    PRODUCT=1d6b/2/414
		    SEQNUM=2168
		    SUBSYSTEM=usb
		    TYPE=9/0/1

Users:		chromium-os-dev@chromium.org

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.