Query: usb_control_msg
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
USB_CONTROL_MSG(9) USB Core APIs USB_CONTROL_MSG(9)NAMEusb_control_msg - Builds a control urb, sends it off and waits for completionSYNOPSISint usb_control_msg(struct usb_device * dev, unsigned int pipe, __u8 request, __u8 requesttype, __u16 value, __u16 index, void * data, __u16 size, int timeout);ARGUMENTSdev pointer to the usb device to send the message to pipe endpoint "pipe" to send the message to request USB message request value requesttype USB message request type value value USB message value index USB message index value data pointer to the data to send size length in bytes of the data to send timeout time in msecs to wait for the message to complete before timing out (if 0 the wait is forever)CONTEXT!in_interrupt ()DESCRIPTIONThis function sends a simple control message to a specified endpoint and waits for the message to complete, or timeout. Don't use this function from within an interrupt context, like a bottom half handler. If you need an asynchronous message, or need to send a message from within interrupt context, use usb_submit_urb. If a thread in your driver uses this call, make sure your disconnect method can wait for it to complete. Since you don't have a handle on the URB used, you can't cancel the request.RETURNIf successful, the number of bytes transferred. Otherwise, a negative error number.COPYRIGHTKernel Hackers Manual 3.10 June 2014 USB_CONTROL_MSG(9)
Related Man Pages |
---|
usb_submit_urb(9) - suse |
usb_control_msg(9) - centos |
usb_interrupt_msg(9) - centos |
usb_set_interface(9) - centos |
usb_sg_init(9) - centos |
Similar Topics in the Unix Linux Community |
---|
please help a problem in client-server ipc message 2 pipes communication simple example |
Flapping (reconnecting) external USB drive |
How to send data to previous program (pipe)? |