From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aneesh V Subject: Re: [RFC PATCH 3/8] misc: emif: add register definitions for EMIF Date: Thu, 09 Feb 2012 19:50:30 +0530 Message-ID: <4F33D62E.8070403@ti.com> References: <331ABD5ECB02734CA317220B2BBEABC1317897B8@DBDE01.ent.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from na3sys009aob106.obsmtp.com ([74.125.149.76]:53838 "EHLO na3sys009aog106.obsmtp.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750811Ab2BIOUh (ORCPT ); Thu, 9 Feb 2012 09:20:37 -0500 Received: by ggnf1 with SMTP id f1so1031264ggn.0 for ; Thu, 09 Feb 2012 06:20:35 -0800 (PST) In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Bedia, Vaibhav" Cc: "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" On Thursday 09 February 2012 04:55 PM, Bedia, Vaibhav wrote: >> -----Original Message----- >> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of V, Aneesh >> Sent: Saturday, February 04, 2012 5:46 PM >> To: linux-omap@vger.kernel.org >> Cc: linux-kernel@vger.kernel.org; akpm@linux-foundation.org; V, Aneesh >> Subject: [RFC PATCH 3/8] misc: emif: add register definitions for EMIF >> > > Sorry for the delayed response. Can these register definitions be put in a place > where the code from the arch/arm/mach-omap2/* can also access it? I don't have any issues with it as long as everybody is in agreement. > > Devices like AM335x and TI814x will need to reconfigure the EMIF when coming out > of low power states and putting these register definitions in a common place > will help us avoid some code duplication. Can you elaborate on that. Does EMIF lose its settings in low-power mode? If so, are you going to do the re-initialization from internal RAM or something? For us EMIF doesn't lose its state in low power modes. br, Aneesh From mboxrd@z Thu Jan 1 00:00:00 1970 From: aneesh@ti.com (Aneesh V) Date: Thu, 09 Feb 2012 19:50:30 +0530 Subject: [RFC PATCH 3/8] misc: emif: add register definitions for EMIF In-Reply-To: References: <331ABD5ECB02734CA317220B2BBEABC1317897B8@DBDE01.ent.ti.com> Message-ID: <4F33D62E.8070403@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thursday 09 February 2012 04:55 PM, Bedia, Vaibhav wrote: >> -----Original Message----- >> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of V, Aneesh >> Sent: Saturday, February 04, 2012 5:46 PM >> To: linux-omap at vger.kernel.org >> Cc: linux-kernel at vger.kernel.org; akpm at linux-foundation.org; V, Aneesh >> Subject: [RFC PATCH 3/8] misc: emif: add register definitions for EMIF >> > > Sorry for the delayed response. Can these register definitions be put in a place > where the code from the arch/arm/mach-omap2/* can also access it? I don't have any issues with it as long as everybody is in agreement. > > Devices like AM335x and TI814x will need to reconfigure the EMIF when coming out > of low power states and putting these register definitions in a common place > will help us avoid some code duplication. Can you elaborate on that. Does EMIF lose its settings in low-power mode? If so, are you going to do the re-initialization from internal RAM or something? For us EMIF doesn't lose its state in low power modes. br, Aneesh