From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH V2 6/8] usb: musb: Offmode fix for idle path Date: Mon, 09 Aug 2010 14:01:26 -0700 Message-ID: <87k4nzijq1.fsf@deeprootsystems.com> References: <1281115624-1174-1-git-send-email-hemahk@ti.com> <4C5FFC25.4060707@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Hema Kalliguddi's message of "Mon, 9 Aug 2010 18:42:34 +0530") Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Kalliguddi, Hema" Cc: "Cousson, Benoit" , "linux-usb@vger.kernel.org" , "linux-omap@vger.kernel.org" , "Mankad, Maulik Ojas" , Felipe Balbi , Tony Lindgren List-Id: linux-omap@vger.kernel.org "Kalliguddi, Hema" writes: [...] >>> >>> Changed the usb sysconfig settings as per the usbotg functional spec. >>> When the device is not active, configure to force idle and >>force standby mode. >>> When it is being used, configure in smart standby and smart >>idle mode. >>> So while attempting to coreoff the usb is configured to >>force standby and >>> force idle mode, after wakeup configured in smart idle and >>smart standby. >> >>Is this valid for OMAP3 and OMAP4? I checked quickly the OMAP4 >>TRM vB in >>the USB_OTG chapter related to PM (23.13.4.2 Power-Management), and I >>cannot find any note regarding that specific programming model. >>Could give us reference to the documentation that contains the details >>about that? >> >>Benoit >> > > This is valid for both OMAP3 and OMAP4. You can find this in 24.1.5.4 section > With different modes. When not used with any application the mode has to be programmed > is force idle and force standby. What I observed is that without this USB was > blocking the coreoff. > > http://focus.ti.com/pdfs/wtbu/SWPU223D_Final_EPDF_06_07_2010.pdf > For the next rev, please include links to public docs in the changelog. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html