linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Vishwanath BS <vishwanath.bs@ti.com>
Cc: linux-omap@vger.kernel.org, linaro-dev@lists.linaro.org,
	Kevin Hillman <khilman@deeprootsystems.com>
Subject: Re: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr
Date: Fri, 24 Sep 2010 12:01:26 -0700	[thread overview]
Message-ID: <20100924190125.GG4211@atomide.com> (raw)
In-Reply-To: <1285325785-6163-2-git-send-email-vishwanath.bs@ti.com>

* Vishwanath BS <vishwanath.bs@ti.com> [100924 03:50]:
> There is no need to keep omap3 sleep code in SRAM. This code can be run very
> well on DDR. This would help us to instrument CPUIdle latencies.

Uhh, are you sure about this? To me it sounds like you're then
relying on the code running from the cache for off-idle?

What about CONFIG_CPU_ICACHE_DISABLE?

Regards,

Tony

  reply	other threads:[~2010-09-24 19:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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:56 ` [PATCH 2/2] OMAP3 PM: sleep code clean up Vishwanath BS
     [not found]   ` <1285325785-6163-3-git-send-email-vishwanath.bs-l0cyMroinI0@public.gmane.org>
2010-09-24 20:05     ` Kevin Hilman
2010-10-04  8:44       ` Sripathy, Vishwanath
2010-10-04  8:56         ` Amit Kucheria
2010-10-04  9:36           ` Shilimkar, Santosh
  -- strict thread matches above, loose matches on Subject: below --
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
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-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=20100924190125.GG4211@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --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).