linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	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 10:13:41 -0800	[thread overview]
Message-ID: <20101118181341.GH9264@atomide.com> (raw)
In-Reply-To: <20101118175215.GE9264@atomide.com>

* Tony Lindgren <tony@atomide.com> [101118 09:42]:
> * Nishanth Menon <nm@ti.com> [101118 08:46]:
> > 
> > But after wfi in wait_sdrc_ok as part of the code executing in SRAM
> > today omap34xx_cpu_suspend -> we are waiting for DPLL3 lock prior to
> > accessing DDR -> how do we execute that logic in SDRAM?
> 
> I too am a bit concerned how this will all keep working. For light
> testing it may be running OK if it happens to run from cache..

This in the retention case, in off-idle those should be powered down..

Tony

  reply	other threads:[~2010-11-18 18:13 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
2010-11-18 16:55       ` Nishanth Menon
2010-11-18 17:52         ` Tony Lindgren
2010-11-18 18:13           ` Tony Lindgren [this message]
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=20101118181341.GH9264@atomide.com \
    --to=tony@atomide.com \
    --cc=j-pihet@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=khilman@deeprootsystems.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).