From mboxrd@z Thu Jan 1 00:00:00 1970 From: Santosh Shilimkar Subject: Re: [PATCH 13/15] ARM: DTS: AM33XX: Add nodes for OCMCRAM and Mailbox Date: Tue, 6 Nov 2012 03:15:10 +0530 Message-ID: <50983366.2020007@ti.com> References: <1351859566-24818-1-git-send-email-vaibhav.bedia@ti.com> <1351859566-24818-14-git-send-email-vaibhav.bedia@ti.com> <50953E26.40906@ti.com> <5097D2D7.3090204@ti.com> <87a9uv97c0.fsf@deeprootsystems.com> <50982D61.9060204@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from devils.ext.ti.com ([198.47.26.153]:34854 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932918Ab2KEVpP (ORCPT ); Mon, 5 Nov 2012 16:45:15 -0500 In-Reply-To: <50982D61.9060204@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Bedia, Vaibhav" Cc: Kevin Hilman , "linux-arm-kernel@lists.infradead.org" , "linux-omap@vger.kernel.org" , "paul@pwsan.com" , "Cousson, Benoit" , "tony@atomide.com" On Tuesday 06 November 2012 02:49 AM, Santosh Shilimkar wrote: > On Tuesday 06 November 2012 12:59 AM, Kevin Hilman wrote: >> "Bedia, Vaibhav" writes: >> >>> On Mon, Nov 05, 2012 at 20:23:11, Shilimkar, Santosh wrote: >>> [...] >>>>> >>>> On OMAP the OCMC RAM is always clocked and doesn't need any special >>>> clock enable. CM_L3_2_OCMC_RAM_CLKCTRL module mode field is read only. >>>> Isn't it same on AMXX ? >>>> >>> >>> On AM33xx, OCMC RAM is in PER domain and the corresponding CLKCLTR >>> module >>> mode fields are r/w. OCMC RAM needs to be disabled as part of the >>> DeepSleep0 >>> entry to let PER domain transition. >> >> After DeepSleep0, the ROM code is being given an address in OCMC RAM to >> jump to. If OCMC RAM is disabled as part of suspend, this means that >> OCMC RAM contents are maintained even though PER domain transitions? >> >> If so, that needs to be more clearly documented. >> > Thats very good point. How does OCMC RAM retains the contents without > clock ? > Ignore the question. I figured out from other patch changelog the OCMC RAM supports retention. Please have that clearly captured in change log. Regards Santosh