Hi Nishant, On Thu, Nov 18, 2010 at 4:11 PM, Nishanth Menon <nm@xxxxxx> wrote: >> -----Original Message----- >> From: Sripathy, Vishwanath [mailto:vishwanath.bs@xxxxxx] >> Sent: Thursday, November 18, 2010 9:09 AM >> To: Nishanth Menon >> Cc: Jean Pihet; linux-omap@xxxxxxxxxxxxxxx; Kevin Hillman; Jean > Pihet-XID >> Subject: Re: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr >> >> NIshant, >> >> On Thu, Nov 18, 2010 at 8:27 PM, Nishanth Menon <nm@xxxxxx> wrote: >> >> -----Original Message----- >> >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >> >> owner@xxxxxxxxxxxxxxx] On Behalf Of Jean Pihet >> >> Sent: Thursday, November 18, 2010 8:52 AM >> >> To: linux-omap@xxxxxxxxxxxxxxx >> >> Cc: Vishwanath BS; Kevin Hillman; Jean Pihet >> >> Subject: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr >> >> >> >> From: Vishwanath BS <vishwanath.bs@xxxxxx> >> >> >> >> For historical reasons the OMAP3 sleep code is run from SRAM. >> >> This code can run from DDR which provides better performance and >> >> leaves the SRAM available for other uses. >> >> >> >> Tested on ZOOM3, OMAP3EVM, Beagleboard, n900 >> >> with full RET and OFF modes. >> > >> > Sorry, But I disagree with this patch. >> > >> > There is a silicon errata which cannot be handled with this - RTA >> disable >> > - errata i608 >> > >> > You need to disable RTA while coming out of OFF - we cannot handle > this >> on >> > >> > GP devices if this is not done. >> When you come out of Core off, SRAM contents are anyway lost. So you >> have to run from DDR after ROM Code completes. This behavior has not >> changed with this patch. I fail to understand your concern here. > I could potentially be mistaken. Let me do one thing - I will post out the > > patches that I have to the list and we can see how this all works > together Ok, fine. I did not find any 36xx specific workaround for the errata i608 issue. Is there one already available? Thanks, Jean > > Regards, > Nishanth Menon > -- 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
