From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Date: Thu, 18 Nov 2010 09:52:15 -0800 Message-ID: <20101118175215.GE9264@atomide.com> References: <1290091906-32539-1-git-send-email-j-pihet@ti.com> <1290091906-32539-2-git-send-email-j-pihet@ti.com> <87tyjey6h3.fsf@deeprootsystems.com> <4CE55A88.6010300@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:52768 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755363Ab0KRRwU (ORCPT ); Thu, 18 Nov 2010 12:52:20 -0500 Content-Disposition: inline In-Reply-To: <4CE55A88.6010300@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Nishanth Menon Cc: Kevin Hilman , Jean Pihet , linux-omap@vger.kernel.org, Vishwanath Sripathy , Jean Pihet-XID * Nishanth Menon [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.. Also, moving the code out of SRAM will limit the options for what we may need to do with DDR or L3. Retention is something to consider, are there issues with that? Regards, Tony