From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3: PM: restrict erratum i443 handling to OMAP3430 only
Date: Thu, 06 Oct 2011 16:53:01 -0700 [thread overview]
Message-ID: <8762k1n0de.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1110061341460.4611@utopia.booyaka.com> (Paul Walmsley's message of "Thu, 6 Oct 2011 13:43:23 -0600 (MDT)")
Paul Walmsley <paul@pwsan.com> writes:
> Based on the documents that I have here, there doesn't appear to be an
> equivalent to erratum i443 for OMAP3630, so restrict this one to OMAP34xx
> chips.
>
> Also, explicitly restrict this erratum to EMU and HS devices.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Kevin Hilman <khilman@ti.com>
> ---
> Unfortunately, I don't have any HS/EMU devices in my testbed, so it's not
> possible for me to test this one on anything but GP chips.
I don't have any 36xx HS/EMU device either, but this erratum does indeed
seem to be 34xx specific.
Barring any objections, I'll queue this for v3.2 (branch: for_3.2/pm-cleanup-2)
Kevin
> arch/arm/mach-omap2/pm34xx.c | 20 +++++++++++---------
> 1 files changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index a6156bd..9e14ae5 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -407,13 +407,14 @@ void omap_sram_idle(void)
> omap3_intc_prepare_idle();
>
> /*
> - * 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 erratum ID i443.
> - * Hence store/restore the SDRC_POWER register here.
> - */
> - if (omap_rev() >= OMAP3430_REV_ES3_0 &&
> - omap_type() != OMAP2_DEVICE_TYPE_GP &&
> + * 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 erratum ID i443.
> + * Hence store/restore the SDRC_POWER register here.
> + */
> + if (cpu_is_omap3430() && omap_rev() >= OMAP3430_REV_ES3_0 &&
> + (omap_type() == OMAP2_DEVICE_TYPE_EMU ||
> + omap_type() == OMAP2_DEVICE_TYPE_SEC) &&
> core_next_state == PWRDM_POWER_OFF)
> sdrc_pwr = sdrc_read_reg(SDRC_POWER);
>
> @@ -430,8 +431,9 @@ void omap_sram_idle(void)
> omap34xx_do_sram_idle(save_state);
>
> /* Restore normal SDRC POWER settings */
> - if (omap_rev() >= OMAP3430_REV_ES3_0 &&
> - omap_type() != OMAP2_DEVICE_TYPE_GP &&
> + if (cpu_is_omap3430() && omap_rev() >= OMAP3430_REV_ES3_0 &&
> + (omap_type() == OMAP2_DEVICE_TYPE_EMU ||
> + omap_type() == OMAP2_DEVICE_TYPE_SEC) &&
> core_next_state == PWRDM_POWER_OFF)
> sdrc_write_reg(sdrc_pwr, SDRC_POWER);
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP3: PM: restrict erratum i443 handling to OMAP3430 only
Date: Thu, 06 Oct 2011 16:53:01 -0700 [thread overview]
Message-ID: <8762k1n0de.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1110061341460.4611@utopia.booyaka.com> (Paul Walmsley's message of "Thu, 6 Oct 2011 13:43:23 -0600 (MDT)")
Paul Walmsley <paul@pwsan.com> writes:
> Based on the documents that I have here, there doesn't appear to be an
> equivalent to erratum i443 for OMAP3630, so restrict this one to OMAP34xx
> chips.
>
> Also, explicitly restrict this erratum to EMU and HS devices.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Kevin Hilman <khilman@ti.com>
> ---
> Unfortunately, I don't have any HS/EMU devices in my testbed, so it's not
> possible for me to test this one on anything but GP chips.
I don't have any 36xx HS/EMU device either, but this erratum does indeed
seem to be 34xx specific.
Barring any objections, I'll queue this for v3.2 (branch: for_3.2/pm-cleanup-2)
Kevin
> arch/arm/mach-omap2/pm34xx.c | 20 +++++++++++---------
> 1 files changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index a6156bd..9e14ae5 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -407,13 +407,14 @@ void omap_sram_idle(void)
> omap3_intc_prepare_idle();
>
> /*
> - * 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 erratum ID i443.
> - * Hence store/restore the SDRC_POWER register here.
> - */
> - if (omap_rev() >= OMAP3430_REV_ES3_0 &&
> - omap_type() != OMAP2_DEVICE_TYPE_GP &&
> + * 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 erratum ID i443.
> + * Hence store/restore the SDRC_POWER register here.
> + */
> + if (cpu_is_omap3430() && omap_rev() >= OMAP3430_REV_ES3_0 &&
> + (omap_type() == OMAP2_DEVICE_TYPE_EMU ||
> + omap_type() == OMAP2_DEVICE_TYPE_SEC) &&
> core_next_state == PWRDM_POWER_OFF)
> sdrc_pwr = sdrc_read_reg(SDRC_POWER);
>
> @@ -430,8 +431,9 @@ void omap_sram_idle(void)
> omap34xx_do_sram_idle(save_state);
>
> /* Restore normal SDRC POWER settings */
> - if (omap_rev() >= OMAP3430_REV_ES3_0 &&
> - omap_type() != OMAP2_DEVICE_TYPE_GP &&
> + if (cpu_is_omap3430() && omap_rev() >= OMAP3430_REV_ES3_0 &&
> + (omap_type() == OMAP2_DEVICE_TYPE_EMU ||
> + omap_type() == OMAP2_DEVICE_TYPE_SEC) &&
> core_next_state == PWRDM_POWER_OFF)
> sdrc_write_reg(sdrc_pwr, SDRC_POWER);
next prev parent reply other threads:[~2011-10-06 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 19:43 [PATCH] ARM: OMAP3: PM: restrict erratum i443 handling to OMAP3430 only Paul Walmsley
2011-10-06 19:43 ` Paul Walmsley
2011-10-06 23:53 ` Kevin Hilman [this message]
2011-10-06 23:53 ` 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=8762k1n0de.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.