On Fri, 2009-02-13 at 14:35 -0800, David Brownell wrote: > On Friday 13 February 2009, Kalle Jokiniemi wrote: > > I ran into some trouble with the merged fix. For some reason clearing > > the VUSB3V1_DEV_GRP register causes VUSB_DEDICATED2.VUSB3V1_SLEEP bit to > > be enabled. This means that once VUSB3V1_DEV_GRP is put back to enabled > > state (VUSB3V1 changed to be part of P1 group again), VUSB3V1 does not > > go ACTIVE, but SLEEP state instead. > > > > Anyone have a clue what might cause this? > > Curious. No ... is that specific to some TWL revision? TWL5030, I think the revision is ES1.0. I got additional info from TI that when the LDO goes into off state, the sleep bit indeed resets back to default value of 1. Which is to remap active state to sleep. So I have a patch that takes this into account by clearing the remap bit every time we wake up the VUSB3V1 regulator. - Kalle > > I'll poke around after I get this new board working better for me. > > - Dave -- 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
