public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP3: PM: Force write last pad config register into save area
Date: Tue, 17 Nov 2009 11:17:00 -0600	[thread overview]
Message-ID: <4B02DA8C.3060801@ti.com> (raw)
In-Reply-To: <1258475693-22068-1-git-send-email-tero.kristo@nokia.com>

Tero Kristo had written, on 11/17/2009 10:34 AM, the following:
> From: Tero Kristo <tero.kristo@nokia.com>
> 
> Due to OMAP3 errata XYZ, the save of the last pad register (ETK_D14 and
> ETK_D15) can fail sometimes when there is simultaneous OCP access to the
> SCM register area. Fixed by writing the last register to the save area.
> 
> Also, optimized the delay loop for the HW save to include an udelay(1),
> which limits the number of unnecessary HW accesses to SCM register area
> during the save.
Nitpicky minor comment: Should we split this out?

Also, this replaces the patch discussed under: 
http://marc.info/?t=125474192000004&r=1&w=2

> 
> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
Acked-by: Nishanth Menon <nm@ti.com>

> ---
>  arch/arm/mach-omap2/pm34xx.c |   10 +++++++++-
>  1 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 4b01303..4ead40e 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -155,7 +155,15 @@ static void omap3_core_save_context(void)
>  	/* wait for the save to complete */
>  	while (!(omap_ctrl_readl(OMAP343X_CONTROL_GENERAL_PURPOSE_STATUS)
>  			& PADCONF_SAVE_DONE))
> -		;
> +		udelay(1);
> +
> +	/*
> +	 * Force write last pad into memory, as this can fail in some
> +	 * cases according to errata XYZ
> +	 */
> +	omap_ctrl_writel(omap_ctrl_readl(OMAP343X_PADCONF_ETK_D14),
> +		OMAP343X_CONTROL_MEM_WKUP + 0x2a0);
> +
>  	/* Save the Interrupt controller context */
>  	omap_intc_save_context();
>  	/* Save the GPMC context */


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2009-11-17 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 16:34 [PATCH] OMAP3: PM: Force write last pad config register into save area Tero Kristo
2009-11-17 17:17 ` Nishanth Menon [this message]
2009-11-17 17:19 ` Gadiyar, Anand
2009-11-17 18:34 ` Kevin Hilman
2009-11-18 12:23   ` Tero.Kristo
2009-11-18 14:11   ` Gopinath, Thara
2009-11-18 14:16     ` Kevin Hilman

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=4B02DA8C.3060801@ti.com \
    --to=nm@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tero.kristo@nokia.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