From: Kevin Hilman <khilman@ti.com>
To: jean.pihet@newoldbits.com
Cc: linux-omap@vger.kernel.org, santosh.shilimkar@ti.com,
Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH] OMAP3: run the ASM sleep code from DDR
Date: Thu, 23 Jun 2011 17:17:47 -0700 [thread overview]
Message-ID: <874o3g6q1g.fsf@ti.com> (raw)
In-Reply-To: <1308300725-12150-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Fri, 17 Jun 2011 10:52:05 +0200")
jean.pihet@newoldbits.com writes:
> From: Jean Pihet <j-pihet@ti.com>
>
> Most of the ASM sleep code (in arch/arm/mach-omap2/sleep34xx.S)
> is copied to internal SRAM and run from there.
> However only a small part of the code really needs to run from internal SRAM.
>
> This fix lets most of the ASM idle code run from the DDR
> in order to minimize the SRAM usage. No performance
> loss or gain can be measured with a 32KHz clock period.
>
> The only pieces of code that are mandatory in SRAM
> are:
> - the i443 erratum WA,
> - the i581 erratum WA,
> - the security extension code.
>
> SRAM usage:
> - original code:
> . 560 bytes for omap3_sram_configure_core_dpll (used by DVFS),
> . 1196 bytes for omap_sram_idle (used by suspend/resume in RETention),
> . 124 bytes for es3_sdrc_fix (used by suspend/resume in OFF mode on ES3.x),
> . 108 bytes for save_secure_ram_context (used on HS parts only).
>
> With this fix the usage for suspend/resume in RETention goes down 288 bytes,
> so the gain in SRAM usage for suspend/resume is 908 bytes.
>
> Also fixed the SRAM initialization sequence to avoid an unnecessary
> copy to SRAM at boot time and for readability.
>
> Tested on Beagleboard (ES2.x) in idle with full RET and OFF modes.
>
> Signed-off-by: Jean Pihet <j-pihet@ti.com>
Hi Jean,
Can you rebase/retest this on top of my pm-wip/idle-suspend branch,
which now contains Russell's major cleanup to use the common code as
well as an additional patch from me to remove the unncessary
get_*_restore_pointer functions:
[PATCH] OMAP3: PM: remove get_*_restore_pointer functions, directly use entry points
Thanks,
Kevin
next prev parent reply other threads:[~2011-06-24 0:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 8:52 [PATCH] OMAP3: run the ASM sleep code from DDR jean.pihet
2011-06-17 9:51 ` Santosh Shilimkar
2011-06-24 0:17 ` Kevin Hilman [this message]
2011-06-24 8:32 ` Jean Pihet
2011-06-24 14:42 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2011-06-29 16:40 jean.pihet
2011-06-29 16:40 ` jean.pihet at newoldbits.com
2011-06-29 17:29 ` Kevin Hilman
2011-06-29 17:29 ` Kevin Hilman
2011-06-29 17:48 ` Jean Pihet
2011-06-29 17:48 ` Jean Pihet
2011-06-29 18:05 ` Russell King - ARM Linux
2011-06-29 18:05 ` Russell King - ARM Linux
2011-06-29 19:06 ` Kevin Hilman
2011-06-29 19:06 ` Kevin Hilman
2011-06-29 21:54 ` Russell King - ARM Linux
2011-06-29 21:54 ` Russell King - ARM Linux
2011-06-29 23:30 ` Kevin Hilman
2011-06-29 23:30 ` Kevin Hilman
2011-06-29 21:45 ` Russell King - ARM Linux
2011-06-29 21:45 ` Russell King - ARM Linux
2011-06-30 8:55 ` Peter De Schrijver
2011-07-12 6:07 ` Pavel Machek
2011-07-12 6:07 ` Pavel Machek
2011-07-13 8:14 ` Paul Walmsley
2011-07-13 8:14 ` Paul Walmsley
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=874o3g6q1g.fsf@ti.com \
--to=khilman@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@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 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.