> -----Original Message----- > From: Kim Kyuwon [mailto:chammoru@xxxxxxxxx] > Sent: Thursday, February 26, 2009 12:28 PM > To: Gadiyar, Anand > Cc: me@xxxxxxxxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx; OMAP; > David Brownell; q1.kim@xxxxxxxxxxx; Minkyu Kang > Subject: Re: [PATCH 1/2] usb: musb: fix the possible panic > while resuming > > Hi, > > On Thu, Feb 26, 2009 at 3:37 PM, Gadiyar, Anand <gadiyar@xxxxxx> wrote: > > <snip> > > > >> Now I know that, in addition to HSUSB_MC_NINT disabled by the previous > >> patch [ARM: OMAP: Disable USB interrupt in the musb_resume() > >> function], USBTLL_SWAKEUP and USBHOST_SWAKEUP can be also wake-up > >> source events to PRMC module. Sorry I didn't know that time. The > >> remote wake uses these two SWAKEUP. David, is my previous patch is > >> still NAK? > > > > USBTLL_SWAKEUP and USBHOST_SWAKEUP are not for MUSB. > > > > But they are used to wake up request. Can I ask what they are for? > I'm not the PRCM expert, but USBHOST refers to EHCI/OHCI and USBTLL is needed for EHCI (except in PHY mode) and for OHCI (all modes). These wakeup sources are meant for wakeups initiated by these modules. MUSB is a different module altogether. -- 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
