On Sat, 2016-10-29 at 22:18 +0200, Christian Lamparter wrote: > On Saturday, October 29, 2016 8:44:27 PM CEST Christian Lamparter wrote: > > [...] > > [ 7.849577] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in > > Host mode > > [ 7.855582] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in > > Host mode > > [ 7.862820] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in > > Host mode > > [ 8.051083] usb 1-1: new high-speed USB device number 2 using dwc2 > > [ 8.055952] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in > > Host mode > > [ 8.063064] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in > > Host mode > > > > Now, there has been recent changes to dwc2 which might fix these pesky > > errors. The discussion can be found on the LKML [3] and three patches > > were committed to 4.9-rc. > > > > usb: dwc2: Properly account for the force mode delays [4] > > usb: dwc2: Add delay to core soft reset [5] > > usb: dwc2: gadget: Only initialize device if in device mode [6] > > > > I'll give then a try and see test if they help. Otherwise: > > Not much. There are now just four "Mode Mismatch Interrupt" instead of five. > > I did a short 400MiB read speed test from a fast usb stick. > The dwc2 driver (with the param_ltq values) is faster than > ifxhcd. > > ifxhcd: > real 0m 23.26s > user 0m 0.01s > sys 0m 15.18s > > dwc2: > real 0m 16.31s > user 0m 0.00s > sys 0m 8.38s > > Regards, > Christian > > > [4] > > <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/dwc2?id=2938fc63e0c26bf694436ac81bc776c8b7eced0c> > > [5] > > <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/dwc2?id=fef6bc37dbafe0d6d71c808c8867a8c5ab4b9816> > > [6] > > <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/dwc2?id=d0f0ac56b34b28e80223d7086b4decdf027c27ed>
Thanks for testing this. It looks like we'll have to live with the "mode mismatch" errors for the moment. I can certainly do a patch to add dr_mode to the dts to get rid of the initial "Configuration mismatch" error at least. The same should also be done on ar9 - I know the error appears there too. What about vrx? _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
