Query: usb_get_status
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
USB_GET_STATUS(9) USB Core APIs USB_GET_STATUS(9)NAMEusb_get_status - issues a GET_STATUS callSYNOPSISint usb_get_status(struct usb_device * dev, int type, int target, void * data);ARGUMENTSdev the device whose status is being checked type USB_RECIP_*; for device, interface, or endpoint target zero (for device), else interface or endpoint number data pointer to two bytes of bitmap dataCONTEXT!in_interrupt ()DESCRIPTIONReturns device, interface, or endpoint status. Normally only of interest to see if the device is self powered, or has enabled the remote wakeup facility; or whether a bulk or interrupt endpoint is halted ("stalled"). Bits in these status bitmaps are set using the SET_FEATURE request, and cleared using the CLEAR_FEATURE request. The usb_clear_halt function should be used to clear halt ("stall") status. This call is synchronous, and may not be used in an interrupt context. Returns 0 and the status value in *data (in host byte order) on success, or else the status code from the underlying usb_control_msg call.COPYRIGHTKernel Hackers Manual 3.10 June 2014 USB_GET_STATUS(9)
Related Man Pages |
---|
usb_bulk_msg(9) - suse |
usb_interrupt_msg(9) - suse |
usb_bulk_msg(9) - centos |
usb_get_status(9f) - sunos |
ubtbcmfw(4) - freebsd |
Similar Topics in the Unix Linux Community |
---|
Weird 'find' results |
DB2 convert digits to binary format |
Tar Command |
Controlling user input |
[TIP] Processing YAML files with yq |