PCI and USB devices in the /sys/devices tree, with uevents and USB hot-plug
PCI devices live at /sys/devices/pci0000:00/<addr> and USB devices under the xHCI controller that carries their bus, below that bus's root hub usbN; /sys/bus/pci/devices and /sys/bus/usb/devices are symlinks into it, and every device has its subsystem and driver links, which is how udev learns SUBSYSTEM and DRIVER. Writing to a device's uevent now announces it with MODALIAS, PCI_ID, PRODUCT and the rest, so udevadm trigger covers them, and the USB core sends add when a device is attached and remove as it goes. The root hub is announced when the controller comes up, before anything is plugged in. Checked under QEMU: lspci and udevadm info through the links, udevadm monitor showing the kernel and udev add event for device_add usb-kbd/usb-mouse and the remove event for device_del, and a triggered add for usb1 and 1-5. Known limits: the bus-to-controller mapping is a convention (bus N is the Nth xHCI in PCI order); PCI bridges are not parents; USB interfaces and /dev/bus/usb nodes are absent; busybox's lsusb reads /dev/bus/usb and prints nothing. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EVRhxi9zpdW2uDUN4FVcao
This commit is contained in:
parent
dee3affa3b
commit
8d836c66b2
8 changed files with 526 additions and 67 deletions
|
|
@ -61,3 +61,10 @@ struct usb_info {
|
|||
char driver[16]; // the first interface's, or empty
|
||||
};
|
||||
int usb_info_nth(int i, struct usb_info *out);
|
||||
// How many USB buses have shown a device so far; bus numbers run 1..this.
|
||||
int usb_nbuses(void);
|
||||
// Tell /sys and udev a USB device appeared ("add") or is about to go ("remove").
|
||||
void sysfs_usb_uevent(const struct usb_info *u, const char *action);
|
||||
void sysfs_usb_root_uevent(int bus, const char *action);
|
||||
// A USB controller is up; number its bus and announce its root hub.
|
||||
void usb_bus_add(void *hc);
|
||||
|
|
|
|||
Loading…
Reference in a new issue