diff options
| author | Douglas Anderson <[email protected]> | 2018-07-26 20:07:29 +0000 |
|---|---|---|
| committer | Felipe Balbi <[email protected]> | 2018-07-30 07:39:19 +0000 |
| commit | 3af0540ad39e0f4935c572ad94f57d5408e95cec (patch) | |
| tree | 9e56d5c150384055ba3de4f2ae33dbcf3a46cbf5 /lib/bitmap.c | |
| parent | usb: dwc2: Turn on uframe_sched on "his" platforms (diff) | |
| download | kernel-3af0540ad39e0f4935c572ad94f57d5408e95cec.tar.gz kernel-3af0540ad39e0f4935c572ad94f57d5408e95cec.zip | |
usb: dwc2: Turn on uframe_sched on "amlogic" platforms
There's no reason to have the uframe scheduler off on dwc2. Running
with uframe_sched = False is equivalent to saying "I don't want to run
the correct code, I want to run the old and incorrect code".
The uframe scheduler has been off on Amlogic since commit f94310ac076e
("usb: dwc2: add support for Meson8b and GXBB SoCs"). While this was
after most of the recent improvements, notably the commit 9f9f09b048f5
("usb: dwc2: host: Totally redo the microframe scheduler"), presumably
the parameters were copied from another platform and the uframe
scheduler wasn't tried.
Presumably if everyone is good w/ the uframe_sched turned back on we
can kill all the old and crufty non-uframe sched code.
Reviewed-by: Minas Harutyunyan <[email protected]>
Signed-off-by: Douglas Anderson <[email protected]>
Signed-off-by: Felipe Balbi <[email protected]>
Diffstat (limited to 'lib/bitmap.c')
0 files changed, 0 insertions, 0 deletions