Felipe Balbi <balbi@xxxxxx> writes:
Felipe Balbi <balbi@xxxxxx> writes:In all fairness, none of these are regressions. Can we agree to look at
Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> writes:We also seem to have issues with Kconfig. If I try to make gadget driver
This is a resurrection of the patches initially submitted by Ruslanthere is one problem with this patchset. If I try to statically link
Bilovol in the following thread: https://lkml.org/lkml/2015/6/22/554
The changes since the original submission (v5) includes rebase onto
latest linux-next branch, simplification of the code requested by Alan
Stern and Felipe Balbi, removal of a patch, which deleted __init/__exit
attributes (this change has been already merged) and fixes of the
checkpatch issues.
This feature is urgently needed, because it is not longer possible to
use workaround to avoid deferred probe in UDC drivers due to
not-yet-probed i2c regulator drivers (for more information see
https://lkml.org/lkml/2015/10/30/374 ).
This patchset has been successfully tested on Odroid XU3 boards with
DWC3 UDC driver being deferred by missing regulator drivers.
gadget drivers, only one can be chosen, even though I can enable both
dwc3 and dummy_hcd just fine. And, actually, this brings another
problem. How do we handle systems which have 2 USB peripheral
controllers (say, 2 instances of dwc3) and choose which gadget driver
will bind to which controller ?
built-in, when compiling I'll get asked again if I want gadget drivers
built-in.
Another one: I just tried dummy_hcd built-in, g_zero built-in, dwc3 as a
module. I can never load anything to dwc3 ;-)
these during v4.5-rc so maybe v4.6 has a final solution ?