"ext Rajendra Nayak" <rnayak@xxxxxx> writes: >> -----Original Message----- >> From: linux-omap-owner@xxxxxxxxxxxxxxx >> [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Jouni Hogander >> Sent: Wednesday, June 25, 2008 2:42 PM >> To: linux-omap@xxxxxxxxxxxxxxx >> Subject: [PATCH 0/7] 34XX: PM: Workarounds to get omap3 to >> retention 3rd. >> >> Hi, >> >> This patch set contains all workarounds that are needed to get omap3 >> to retention. Also patch from Tero Kristo to get PM to work if using >> serial console is included in this set. Basically all patches in this >> set should be reverted one by one as correct fixes are implemented and >> applied. >> >> This patch set superseeds earlier version sent 2008-06-17 7:28:35. >> >> To get Omap into retention, this patch set still depends on: >> 1. ARCH: OMAP: MUSB: Do not block sleep (Felipe Balbi) >> 2. ARM: OMAP: SmartReflex driver: enable in >> omap_3430sdp_defconfig (Kalle >> Jokiniemi) >> 3. PRCM: 34XX: Fix wrong shift value used in dpll4_m4x2_ck enable bit >> 4. Patch which removes control of usbhost_sar_fck from clock >> tree (Paul >> Walmsley will send this soon) > > I tried these steps on the 3430SDP but could'nt hit retention. > What is the 4th patch mentioned above which Paul is yet to send and > how does not having it prevent retention? You can do something like this while waiting for patches from Paul: diff --git a/arch/arm/mach-omap2/clock34xx.h b/arch/arm/mach-omap2/clock34xx.h index b4dceea..8370f8a 100644 --- a/arch/arm/mach-omap2/clock34xx.h +++ b/arch/arm/mach-omap2/clock34xx.h @@ -2237,7 +2237,7 @@ static struct clk usbhost_sar_fck = { .init = &omap2_init_clk_clkdm, .enable_reg = OMAP34XX_PRM_REGADDR(OMAP3430ES2_USBHOST_MOD, PM_PWSTCTRL), .enable_bit = OMAP3430ES2_SAVEANDRESTORE_SHIFT, - .flags = CLOCK_IN_OMAP3430ES2, + .flags = CLOCK_IN_OMAP3430ES2 | ALWAYS_ENABLED, .clkdm_name = "usbhost_clkdm", .recalc = &followparent_recalc, }; -- Jouni Högander -- 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
