Hi
On Wed, Nov 27, 2013 at 4:26 PM, Michael Trimarchi
<michael@xxxxxxxxxxxxxxxxxxxx> wrote:
> Hi Felipe,
>
> I'm trying to understand how dpll_usb and vbus should work in suspend mode.
> What I have in my kernel 3.0.31 from ti is that if I suspend the device with id
> pin ground and no device connected I have:
>
> - vbus 5v
> - dpll_usb locked problem so l3domain can not suspend
>
> If I have the id pin floating (device mode) and no device connected I
> can suspend
> without problem. I'm not care about remote wakeup and I would like to understand
> what is the reason of having no complete suspend in host mode. Can you give
> some insight?
I get a bit further and if I do something like that so basically force
device mode I can suspend.
+ if (val) {
+ twl->force_device = false;
+ twl6030_writeb(twl, TWL_MODULE_USB, 0x14, USB_ID_CTRL_SET);
+ twl6030_usb_irq(twl->irq2, twl);
+ twl6030_usbotg_irq(twl->irq1, twl);
+ } else {
+ twl->force_device = true;
+ twl6030_writeb(twl, TWL_MODULE_USB, 0x14, USB_ID_CTRL_CLR);
+ twl6030_usb_irq(twl->irq2, twl);
+ twl6030_usbotg_irq(twl->irq1, twl);
+ }
So my problem is let the device connect host mode (remote wakeup
disable) and let the system suspend in the correct way.
Michael
>
> Michael
--
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
