Query: usb_make_path
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
USB_MAKE_PATH(9) Host-Side Data Types and Macro USB_MAKE_PATH(9)NAMEusb_make_path - returns stable device path in the usb treeSYNOPSISint usb_make_path(struct usb_device * dev, char * buf, size_t size);ARGUMENTSdev the device whose path is being constructed buf where to put the string size how big is "buf"?RETURNLength of the string (> 0) or negative if size was too small.NOTEThis identifier is intended to be "stable", reflecting physical paths in hardware such as physical bus addresses for host controllers or ports on USB hubs. That makes it stay the same until systems are physically reconfigured, by re-cabling a tree of USB devices or by moving USB host controllers. Adding and removing devices, including virtual root hubs in host controller driver modules, does not change these path identifiers; neither does rebooting or re-enumerating. These are more useful identifiers than changeable ("unstable") ones like bus numbers or device addresses. With a partial exception for devices connected to USB 2.0 root hubs, these identifiers are also predictable. So long as the device tree isn't changed, plugging any USB device into a given hub port always gives it the same path. Because of the use of "companion" controllers, devices connected to ports on USB 2.0 root hubs (EHCI host controllers) will get one path ID if they are high speed, and a different one if they are full or low speed.COPYRIGHTKernel Hackers Manual 3.10 June 2014 USB_MAKE_PATH(9)
Related Man Pages |
---|
ehci(4) - minix |
hubd(7d) - centos |
hubd(7d) - php |
hubd(7d) - mojave |
hubd(7d) - bsd |
Similar Topics in the Unix Linux Community |
---|
USB Devices |
Storage paths |
Help with Porting USB Host Stack to VXWORKS 653 OS+HPCNET8641D |
how to watch the usb port |