> Il giorno 27 mar 2017, alle ore 16:30, Tony Lindgren <tony@xxxxxxxxxxx> ha scritto: > > […] > I wonder if the following test patch allows the mode changing > devices to been properly found? Of course it's just for testing, > and scanning for devices takes now 5 seconds.. But it might > provide clues why musb thinks no devices are connected and we > cut VBUS. > > […] Hi Tony, thanks for your patch. I tested it with both current mainline kernel and my “production” kernel (4.9.13): they have the same behaviour. During boot, vbus is first asserted, then removed for a slightly longer time than before (most likely 5 seconds now), then reasserted. When my device is mode-switched, it is working properly with your patch. If I understood your patch, however, if the device (anyone, not just my one) takes longer to switch, VBUS is deasserted anyway. Although this patch is working for me, personally I would prefer a solution which would not deassert VBUS. At least on a host only port. Honestly I don’t know how a dual role port should work. Regards, Moreno -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
