diff options
| author | Douglas Anderson <dianders@chromium.org> | 2018-07-26 23:07:27 +0300 |
|---|---|---|
| committer | Felipe Balbi <felipe.balbi@linux.intel.com> | 2018-07-30 10:39:19 +0300 |
| commit | b6de7b8c38e99eee5d5ef673f2ff63c982ef608c (patch) | |
| tree | ee12421cd31ddb995fa4a3d8bebdee68911b0e05 /mm/cma.c | |
| parent | 4d4f1e79b800c80313280eec1af25a242a50dce5 (diff) | |
| download | linux-b6de7b8c38e99eee5d5ef673f2ff63c982ef608c.tar.xz | |
usb: dwc2: Turn on uframe_sched on "bcm" 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 Broadcom since commit
58b179dcf28c ("staging: dwc2: disable uframe_sched on the bcm2835").
Since then there have been many many improvements, notably the commit
9f9f09b048f5 ("usb: dwc2: host: Totally redo the microframe
scheduler")
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 <hminas@synopsys.com>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Diffstat (limited to 'mm/cma.c')
0 files changed, 0 insertions, 0 deletions