Sponsored Content
Full Discussion: Gollum
The Lounge What is on Your Mind? Chat with iBot - Our RSS Robot Girl Gollum Post 302086331 by cwang on Wednesday 23rd of August 2006 11:47:23 AM
Old 08-23-2006
Quote:
Originally Posted by Gollum
Tell me more. Thank you for your request.

They are not available right now, would you like to wait?
sure i'll wait, just don't put me on hold
 
USB_INTERRUPT_MSG(9)						   USB Core APIs					      USB_INTERRUPT_MSG(9)

NAME
usb_interrupt_msg - Builds an interrupt urb, sends it off and waits for completion SYNOPSIS
int usb_interrupt_msg(struct usb_device * usb_dev, unsigned int pipe, void * data, int len, int * actual_length, int timeout); ARGUMENTS
usb_dev pointer to the usb device to send the message to pipe endpoint "pipe" to send the message to data pointer to the data to send len length in bytes of the data to send actual_length pointer to a location to put the actual length transferred in bytes timeout time in msecs to wait for the message to complete before timing out (if 0 the wait is forever) CONTEXT
!in_interrupt () DESCRIPTION
This function sends a simple interrupt message to a specified endpoint and waits for the message to complete, or timeout. If successful, it returns 0, otherwise a negative error number. The number of actual bytes transferred will be stored in the actual_length paramater. 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. COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 USB_INTERRUPT_MSG(9)
All times are GMT -4. The time now is 10:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy