Query: usb_block_urb
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
USB_BLOCK_URB(9) USB Core APIs USB_BLOCK_URB(9)NAMEusb_block_urb - reliably prevent further use of an URBSYNOPSISvoid usb_block_urb(struct urb * urb);ARGUMENTSurb pointer to URB to be blocked, may be NULLDESCRIPTIONAfter the routine has run, attempts to resubmit the URB will fail with error -EPERM. Thus even if the URB's completion handler always tries to resubmit, it will not succeed and the URB will become idle. The URB must not be deallocated while this routine is running. In particular, when a driver calls this routine, it must insure that the completion handler cannot deallocate the URB.COPYRIGHTKernel Hackers Manual 3.10 June 2014 USB_BLOCK_URB(9)
Related Man Pages |
---|
usb_interrupt_msg(9) - suse |
usb_submit_urb(9) - suse |
usb_buffer_map_sg(9) - centos |
usb_bulk_msg(9) - centos |
usb_control_msg(9) - centos |
Similar Topics in the Unix Linux Community |
---|
Tar Command |
CentOS7 restoring file capabilities |
Unsure why access time on a directory change isn't changing |
Controlling user input |
[TIP] Processing YAML files with yq |