On Wed, Jul 01, 2009 at 06:19:56PM +0200, Valentin Longchamp wrote: > Daniel Mack wrote: >> I still got trouble with that on my board and I can't really figure out >> what the problem is. Adding an mdelay() here gives some improvement, but >> for the OTG port, I still get 0x24e4/0x2524 as ID in the xvcr's init >> function, but I'm not totally sure I can rule out the hardware. That's >> why I was asking for more testers. > > I also need a mdelay(10) on my board at the exact same place. I think it > would be better to put it into the driver code than into the platform > code (if all platforms need it). Ok. Sascha, in case of no more objections about the patch set, could you do that on-the-fly when commiting? Thanks, Daniel -- 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
