Query: usb_set_device_state
OS: suse
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
USB_SET_DEVICE_STATE(9) USB Core APIs USB_SET_DEVICE_STATE(9)NAMEusb_set_device_state - change a device's current state (usbcore, hcds)SYNOPSISvoid usb_set_device_state(struct usb_device * udev, enum usb_device_state new_state);ARGUMENTSudev pointer to device whose state should be changed new_state new state value to be storedDESCRIPTIONudev->state is _not_ fully protected by the device lock. Although most transitions are made only while holding the lock, the state can can change to USB_STATE_NOTATTACHED at almost any time. This is so that devices can be marked as disconnected as soon as possible, without having to wait for any semaphores to be released. As a result, all changes to any device's state must be protected by the device_state_lock spinlock. Once a device has been added to the device tree, all changes to its state should be made using this routine. The state should _not_ be set directly. If udev->state is already USB_STATE_NOTATTACHED then no change is made. Otherwise udev->state is set to new_state, and if new_state is USB_STATE_NOTATTACHED then all of udev's descendants' states are also set to USB_STATE_NOTATTACHED.COPYRIGHTKernel Hackers Manual 2.6. July 2010 USB_SET_DEVICE_STATE(9)
Related Man Pages |
---|
systemd.device(5) - debian |
struct_usb_device_driver(9) - suse |
systemd.device(5) - mojave |
systemd.device(5) - posix |
systemd.device(5) - xfree86 |
Similar Topics in the Unix Linux Community |
---|
How to restrict user to a specific directory in solaris 10 |
Migrating to UNIX |
Update kernel Linux without reboot?! |
SOCKS proxy & PAM configuration exposure |
Docker learning Phase-I |