On Tue, Oct 27, 2020 at 10:13 PM Ferry Toth <fntoth@xxxxxxxxx> wrote: > Op 22-10-2020 om 15:43 schreef Andy Shevchenko: > > On Thu, Oct 22, 2020 at 4:21 PM Thinh Nguyen <Thinh.Nguyen@xxxxxxxxxxxx> wrote: > >> Ferry Toth wrote: ... > >> There are some fixes to dwc3 in kernel mainline. Is it possible to test > >> this against linux-next? > > I think the best is to wait for v5.10-rc1 and retest. Can you give a try of v5.10-rc1? > I looks like there have been at least 3 problems: > > 1) dwc3 was not working in host mode, but not causing an oops. This may > have been caused by platform changes. Andy has provided a fix for this, > dwc3 now working in host mode on 5.9 Rafael took the above mentioned change(s) for v5.10-rcX. https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=99aed9227073fb34ce2880cbc7063e04185a65e1 > 2) dwc3 was causing the oops in gadget mode as referenced in this > thread. The experimental patch from Jack Phan indeed fixes this. > > Code here: https://github.com/edison-fw/linux/commits/eds-acpi-5.9.0 > > 3) With the above 2 fixes gadgets work but seem to be powered down > (after 15 sec. or so) and up (after 1 sec.) continuously. No oops, no > errors in journal. The gadgets I enabled are a network, sound and mass > storage. The latter stops working due to going up/down quickly. But my > host shows network/sound appearing/disappearing. Journal of edison shows: > > systemd-networkd[525]: usb0: Gained carrier > systemd-networkd[525]: usb0: Gained IPv6LL > systemd-networkd[525]: usb0: Lost carrier > systemd-networkd[525]: usb0: Gained carrier > systemd-networkd[525]: usb0: Gained IPv6LL > systemd-networkd[525]: usb0: Lost carrier > > Any ideas how to proceed are highly welcomed! -- With Best Regards, Andy Shevchenko
