> > > > > > > Yes, it has already implemented at ci_usc_vbus_session. > > > > > I see the code path in ci_udc_vbus_session of udc.c to trigger such > > > an event, but unfortunately it was never possible to run into that > code. > > > > > > The function ci_otg_work in otg.c is prepared to do that in case the > > > irq got triggered by OTGSC_BSVIS bit change. > > > > > > This is true for plugging, but never happened to be called on > unplugging. > > > Is there anything missing to get this working? Or is this completely > > > impossible by the core? I was already fiddling around with the other > > > irq cases OTGSC_*IE, but never got anything useful. > > > > Once the vbus lower than B_SESSION_VALID, it will trigger (set > > OTGSC_BSVIS too) BSV interrupt. > > By theory! ;) > > > Check your vbus after unplugging please. > > Today I measured the voltage level on vbus and it still had ~2.6V while > being not connected to anything. > > > > I am working on the imx25 otg capable SoC. > > I validated this with two different imx25 boards and realized, that we > have this external vbus divider errata for that SoC. > > Errata: ENGcm09152 > > Its likely that the issue is related to this problem as the vbus was not > connected to anything different, than the SoC in that case. > Check the voltage at both cpu side (otgsc get value from it) and connector. check if you have a big cap at vbus. check if set otgsc.vd makes things different Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
