From: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
To: Roger Quadros <ext-roger.quadros@nokia.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
Rajendra Nayak <rnayak@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC][PATCH] OMAP3: PM: Fix workaround implementation for OMAP3 errata (1.142)
Date: Fri, 7 Aug 2009 09:16:24 +0300 [thread overview]
Message-ID: <1249625784.6485.249.camel@ubuntu> (raw)
In-Reply-To: <87tz0k614d.fsf@deeprootsystems.com>
On Fri, 2009-08-07 at 01:14 +0300, Kevin Hilman wrote:
> Roger Quadros <ext-roger.quadros@nokia.com> writes:
>
> > As per errata 1.142, on EMU/HS devices, SDRC_POWER should be programmed
> > for automatic self-refresh before transition to OFF mode.
> > In the current implementation this is done in omap3_scratchpad_contents()
> > which is wrong, since this is the value that will be restored while
> > resuming from OFF mode and not while transitioning to it.
> >
> > This patch implements the workaround in the correct way as per errata.
> >
> > Signed-off-by: Roger Quadros <ext-roger.quadros@nokia.com>
>
> This looks right to me.
>
> Rajendra, Kalle, any comments? since you were the originators of
> the original patch.
>
> Kevin
>
> > ---
> > arch/arm/mach-omap2/control.c | 16 ++--------------
> > arch/arm/mach-omap2/pm34xx.c | 20 ++++++++++++++------
> > 2 files changed, 16 insertions(+), 20 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/control.c b/arch/arm/mach-omap2/control.c
> > index a7159a9..0a563c8 100644
> > --- a/arch/arm/mach-omap2/control.c
> > +++ b/arch/arm/mach-omap2/control.c
> > @@ -272,20 +272,8 @@ void omap3_save_scratchpad_contents(void)
> > (sdrc_read_reg(SDRC_ERR_TYPE) & 0xFFFF);
> > sdrc_block_contents.dll_a_ctrl = sdrc_read_reg(SDRC_DLLA_CTRL);
> > sdrc_block_contents.dll_b_ctrl = 0x0;
> > - /*
> > - * Due to a OMAP3 errata (1.142), on EMU/HS devices SRDC should
> > - * be programed to issue automatic self refresh on timeout
> > - * of AUTO_CNT = 1 prior to any transition to OFF mode.
> > - */
> > - if ((omap_type() != OMAP2_DEVICE_TYPE_GP)
> > - && (omap_rev() >= OMAP3430_REV_ES3_0))
> > - sdrc_block_contents.power = (sdrc_read_reg(SDRC_POWER) &
> > - ~(SDRC_POWER_AUTOCOUNT_MASK|
> > - SDRC_POWER_CLKCTRL_MASK)) |
> > - (1 << SDRC_POWER_AUTOCOUNT_SHIFT) |
> > - SDRC_SELF_REFRESH_ON_AUTOCOUNT;
> > - else
> > - sdrc_block_contents.power = sdrc_read_reg(SDRC_POWER);
> > +
> > + sdrc_block_contents.power = sdrc_read_reg(SDRC_POWER);
Why do you want to remove the workaround from scratchpad?
When we wake up from off mode, the boot ROM code writes these settings
as the first sdrc_power settings after wakeup. If that setting does not
include the workaround, we'll have a period of time where sdram is not
being refreshed. This hits especially HS devices that do long secure
context restore in ROM code as well.
> >
> > sdrc_block_contents.cs_0 = 0x0;
> > sdrc_block_contents.mcfg_0 = sdrc_read_reg(SDRC_MCFG_0);
> > diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> > index 14f10bc..eb3c9e5 100644
> > --- a/arch/arm/mach-omap2/pm34xx.c
> > +++ b/arch/arm/mach-omap2/pm34xx.c
> > @@ -405,15 +405,23 @@ void omap_sram_idle(void)
> > }
> >
> > /*
> > - * On EMU/HS devices ROM code restores a SRDC value
> > - * from scratchpad which has automatic self refresh on timeout
> > - * of AUTO_CNT = 1 enabled. This takes care of errata 1.142.
> > - * Hence store/restore the SDRC_POWER register here.
> > - */
> > + * Due to a OMAP3 errata (1.142), on EMU/HS devices SRDC should
> > + * be programed to issue automatic self refresh on timeout
> > + * of AUTO_CNT = 1 prior to any transition to OFF mode.
> > + */
> > +
> > if (omap_rev() >= OMAP3430_REV_ES3_0 &&
> > omap_type() != OMAP2_DEVICE_TYPE_GP &&
> > - core_next_state == PWRDM_POWER_OFF)
> > + core_next_state == PWRDM_POWER_OFF) {
> > +
> > sdrc_pwr = sdrc_read_reg(SDRC_POWER);
> > + sdrc_write_reg((sdrc_pwr &
> > + ~(SDRC_POWER_AUTOCOUNT_MASK|
> > + SDRC_POWER_CLKCTRL_MASK)) |
> > + (1 << SDRC_POWER_AUTOCOUNT_SHIFT) |
> > + SDRC_SELF_REFRESH_ON_AUTOCOUNT,
> > + SDRC_POWER);
> > + }
This part seems ok to me.
- Kalle
> >
> > if (regset_save_on_suspend)
> > pm_dbg_regset_save(1);
> > --
> > 1.6.0.4
next prev parent reply other threads:[~2009-08-07 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 13:16 [RFC][PATCH] OMAP3: PM: Fix workaround implementation for OMAP3 errata (1.142) Roger Quadros
2009-08-06 22:14 ` Kevin Hilman
2009-08-07 6:16 ` Kalle Jokiniemi [this message]
2009-08-07 8:03 ` Roger Quadros
2009-08-07 8:28 ` Kalle Jokiniemi
2009-08-07 8:48 ` Roger Quadros
2009-08-07 10:30 ` Kalle Jokiniemi
2009-08-07 10:54 ` Roger Quadros
2009-08-07 11:16 ` Kalle Jokiniemi
2009-08-13 15:31 ` Nayak, Rajendra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1249625784.6485.249.camel@ubuntu \
--to=kalle.jokiniemi@digia.com \
--cc=ext-roger.quadros@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox