On Thu, Apr 10, 2008 at 07:24:50PM +0800, Bryan Wu wrote: > I think this kind of devices maybe should be added to the blacklist of > the musb otg driver. > > Do you guys have some idea about that? overcurrent protection is triggering fine, that's why you're getting vbus_err. Blacklist shouldn't be in the kernel, what we should do is just notify the user about this error (needed for otg certification) but never blacklist anything. On the other hand, musb core seems to behave in a quite silly way when it comes to current spikes on read/write operations (after enumeration and after you can access the device). It should rely on its capacitors on case of vbus drop and only trigger vbus_err interrupt if it really couldn't recover from it after capacitors are discharged otherwise it should stay silently and filter out such current spikes. I'm still looking into how to filter this out in software but it's been quite a challenge as you noticed yourself. Let's try to keep going on this, otherwise user experience will be awful with several mass storage devices. -- Best Regards, Felipe Balbi me@xxxxxxxxxxxxxxx http://blog.felipebalbi.com -- 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