From: Kevin Hilman <khilman@deeprootsystems.com>
To: Nishanth Menon <nm@ti.com>
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
linux-omap@vger.kernel.org,
Vishwanath Sripathy <vishwanath.bs@ti.com>,
Jean Pihet-XID <j-pihet@ti.com>
Subject: Re: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr
Date: Thu, 18 Nov 2010 07:52:24 -0800 [thread overview]
Message-ID: <87tyjey6h3.fsf@deeprootsystems.com> (raw)
In-Reply-To: <d2e0f972ca73d80e4929b605a9c2475f@mail.gmail.com> (Nishanth Menon's message of "Thu, 18 Nov 2010 08:57:10 -0600")
Nishanth Menon <nm@ti.com> writes:
>> From: Vishwanath BS <vishwanath.bs@ti.com>
>>
>> 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.
You need to provide some more details here as to exactly why this patch
prevents the ability to do this workaround.
As Vishwa pointed out, when returning from OFF mode, current code
already starts in DDR since SRAM is lost. The current code also already
can jump back into SRAM for certain errata/fixup (c.f. es3_sdrc_fix in
current code.)
Kevin
next prev parent reply other threads:[~2010-11-18 15:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 14:51 OMAP3 sleep code clean-up Jean Pihet
2010-11-18 14:51 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Jean Pihet
2010-11-18 14:57 ` Nishanth Menon
2010-11-18 15:08 ` Sripathy, Vishwanath
2010-11-18 15:11 ` Nishanth Menon
2010-11-18 15:15 ` Jean Pihet
2010-11-18 15:33 ` Nishanth Menon
2010-11-18 15:52 ` Kevin Hilman [this message]
2010-11-18 16:55 ` Nishanth Menon
2010-11-18 17:52 ` Tony Lindgren
2010-11-18 18:13 ` Tony Lindgren
2010-11-18 18:15 ` Jean Pihet
2010-11-18 18:27 ` Tony Lindgren
2010-11-18 18:34 ` Jean Pihet
2010-11-19 15:37 ` Jean Pihet
2010-11-19 16:09 ` Tony Lindgren
2010-11-19 16:14 ` Derrick, David
2010-11-19 16:26 ` Jean Pihet
2010-11-22 10:07 ` Peter 'p2' De Schrijver
2010-11-22 16:03 ` Kevin Hilman
2010-11-22 16:08 ` Jean Pihet
2010-11-22 16:22 ` Peter 'p2' De Schrijver
2010-11-22 16:25 ` Nishanth Menon
2010-11-22 18:23 ` Kevin Hilman
2010-11-22 18:31 ` Nishanth Menon
2010-11-18 14:51 ` [PATCH 2/2] OMAP3: clean up ASM idle code Jean Pihet
2010-11-18 17:41 ` Tony Lindgren
2010-11-18 18:19 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 10:56 [PATCH 0/2] OMAP3 PM: sleep code clean up Vishwanath BS
2010-09-24 10:56 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Vishwanath BS
2010-09-24 19:01 ` Tony Lindgren
2010-09-24 19:09 ` Tony Lindgren
[not found] ` <20100924190930.GH4211-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-09-25 5:52 ` Shilimkar, Santosh
2010-09-24 19:57 ` Kevin Hilman
2010-10-04 7:26 ` Sripathy, Vishwanath
2010-09-24 10:47 [PATCH 0/2] OMAP3 PM: sleep code clean up Vishwanath BS
2010-09-24 10:47 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Vishwanath BS
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=87tyjey6h3.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=vishwanath.bs@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;
as well as URLs for NNTP newsgroup(s).