From mboxrd@z Thu Jan 1 00:00:00 1970 From: Santosh Shilimkar Subject: Re: [PATCH 09/15] ARM: OMAP4+: PM: Restore CPU power state to ON with clockdomain force wakeup method Date: Sat, 2 Mar 2013 11:46:13 +0530 Message-ID: <5131992D.2080006@ti.com> References: <1362139864-9233-1-git-send-email-santosh.shilimkar@ti.com> <1362139864-9233-10-git-send-email-santosh.shilimkar@ti.com> <20130301215315.GA23856@kahuna> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from devils.ext.ti.com ([198.47.26.153]:48487 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751164Ab3CBGOn (ORCPT ); Sat, 2 Mar 2013 01:14:43 -0500 In-Reply-To: <20130301215315.GA23856@kahuna> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Nishanth Menon Cc: linux-omap@vger.kernel.org, khilman@deeprootsystems.com, linux-arm-kernel@lists.infradead.org On Saturday 02 March 2013 03:23 AM, Nishanth Menon wrote: > On 17:40-20130301, Santosh Shilimkar wrote: >> While waking up CPU from off state using clock domain force wakeup, restore >> the CPU power state to ON state before putting CPU clock domain under >> hardware control. Otherwise CPU wakeup might fail. The change is recommended\ > the trailing \ was unintentional I suppose. Yes.. >> for all OMAP4+ devices though the PRCM weakness was observed on OMAP5 >> devices first. >> >> So update the code accordingly. >> >> Signed-off-by: Santosh Shilimkar >> --- [..] > Otherwise: > Acked-by: Nishanth Menon > Thanks