diff options
| author | Douglas Anderson <dianders@chromium.org> | 2016-01-29 05:20:10 +0300 |
|---|---|---|
| committer | Felipe Balbi <balbi@kernel.org> | 2016-03-04 16:14:44 +0300 |
| commit | fae4e82609b0887d6d675170d0c20b6af45d83ba (patch) | |
| tree | d765ea7f3d85865c47ad4308eff9ee4f49a6634c /lib/timerqueue.c | |
| parent | fb616e3f837eee20cc0c6d5866983f7d2730d5a3 (diff) | |
| download | linux-fae4e82609b0887d6d675170d0c20b6af45d83ba.tar.xz | |
usb: dwc2: host: Add dwc2_hcd_get_future_frame_number() call
As we start getting more exact about our scheduling it's becoming more
and more important to know exactly how far through the current frame we
are. This lets us make decisions about whether there's still time left
to start a new transaction in the current frame.
We'll add dwc2_hcd_get_future_frame_number() which will tell you what
the frame number will be a certain number of microseconds (us) from
now. We can use this information to help decide if there's enough time
left in the frame for a transaction that will take a certain duration.
This is expected to be used by a future change ("usb: dwc2: host:
Properly set even/odd frame").
Acked-by: John Youn <johnyoun@synopsys.com>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Tested-by: Heiko Stuebner <heiko@sntech.de>
Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
Signed-off-by: Felipe Balbi <balbi@kernel.org>
Diffstat (limited to 'lib/timerqueue.c')
0 files changed, 0 insertions, 0 deletions