i2o_msg_post_wait_complete(9) [suse man page]

I2O_MSG_POST_WAIT_CO(9) 				       Message-based devices					   I2O_MSG_POST_WAIT_CO(9)

NAME

       i2o_msg_post_wait_complete - Reply to a i2o_msg_post request from IOP

SYNOPSIS

       int i2o_msg_post_wait_complete(struct i2o_controller * c, u32 m, struct i2o_message * msg, u32 context);

ARGUMENTS

       c
	   I2O controller which answers

       m
	   message id

       msg
	   pointer to the I2O reply message

       context
	   transaction context of request

DESCRIPTION

       This function is called in interrupt context only. If the reply reached before the timeout, the i2o_exec_wait struct is filled with the
       message and the task will be waked up. The task is now responsible for returning the message m back to the controller! If the message
       reaches us after the timeout clean up the i2o_exec_wait struct (including allocated DMA buffer).

       Return 0 on success and if the message m should not be given back to the I2O controller, or >0 on success and if the message should be
       given back afterwords. Returns negative error code on failure. In this case the message must also be given back to the controller.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						   I2O_MSG_POST_WAIT_CO(9)

USB_CONTROL_MSG(9)						   USB Core APIs						USB_CONTROL_MSG(9)

NAME

       usb_control_msg - Builds a control urb, sends it off and waits for completion

SYNOPSIS

       int usb_control_msg(struct usb_device * dev, unsigned int pipe, __u8 request, __u8 requesttype, __u16 value, __u16 index, void * data,
			   __u16 size, int timeout);

ARGUMENTS

       dev
	   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 ()

DESCRIPTION

       This function sends a simple control message to a specified endpoint and waits for the message to complete, or timeout.

       If successful, it returns the number of bytes transferred, otherwise a negative error number.

       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_CONTROL_MSG(9)