'\" t .\" Title: usb_get_current_frame_number .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: May 2018 .\" Manual: USB Core APIs .\" Source: Kernel Hackers Manual 3.16.56 .\" Language: English .\" .TH "USB_GET_CURRENT_FRAM" "9" "May 2018" "Kernel Hackers Manual 3\&.16\&" "USB Core APIs" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" usb_get_current_frame_number \- return current bus frame number .SH "SYNOPSIS" .HP \w'int\ usb_get_current_frame_number('u .BI "int usb_get_current_frame_number(struct\ usb_device\ *\ " "dev" ");" .SH "ARGUMENTS" .PP \fIdev\fR .RS 4 the device whose bus is being queried .RE .SH "RETURN" .PP The current frame number for the USB host controller used with the given USB device\&. This can be used when scheduling isochronous requests\&. .SH "NOTE" .PP Different kinds of host controller have different \(lqscheduling horizons\(rq\&. While one type might support scheduling only 32 frames into the future, others could support scheduling up to 1024 frames into the future\&. .SH "COPYRIGHT" .br