blk_end_request(9) [suse man page]

BLK_END_REQUEST(9)						   Block Devices						BLK_END_REQUEST(9)

NAME

       blk_end_request - Helper function for drivers to complete the request.

SYNOPSIS

       bool blk_end_request(struct request * rq, int error, unsigned int nr_bytes);

ARGUMENTS

       rq
	   the request being processed

       error

	   0 for success, < 0 for error

       nr_bytes
	   number of bytes to complete

DESCRIPTION

       Ends I/O on a number of bytes attached to rq. If rq has leftover, sets it up for the next range of segments.

RETURN

       false - we are done with this request true - still buffers pending for this request

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							BLK_END_REQUEST(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)