* [RFC PATCH 3/8] misc: emif: add register definitions for EMIF [not found] <331ABD5ECB02734CA317220B2BBEABC1317897B8@DBDE01.ent.ti.com> @ 2012-02-09 11:25 ` Bedia, Vaibhav 2012-02-09 14:20 ` Aneesh V 0 siblings, 1 reply; 3+ messages in thread From: Bedia, Vaibhav @ 2012-02-09 11:25 UTC (permalink / raw) To: linux-arm-kernel > -----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? 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. Regards, Vaibhav ^ permalink raw reply [flat|nested] 3+ messages in thread
* [RFC PATCH 3/8] misc: emif: add register definitions for EMIF 2012-02-09 11:25 ` [RFC PATCH 3/8] misc: emif: add register definitions for EMIF Bedia, Vaibhav @ 2012-02-09 14:20 ` Aneesh V 2012-02-09 14:44 ` Bedia, Vaibhav 0 siblings, 1 reply; 3+ messages in thread From: Aneesh V @ 2012-02-09 14:20 UTC (permalink / raw) To: linux-arm-kernel 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* [RFC PATCH 3/8] misc: emif: add register definitions for EMIF 2012-02-09 14:20 ` Aneesh V @ 2012-02-09 14:44 ` Bedia, Vaibhav 0 siblings, 0 replies; 3+ messages in thread From: Bedia, Vaibhav @ 2012-02-09 14:44 UTC (permalink / raw) To: linux-arm-kernel On Thu, Feb 09, 2012 at 19:50:30, V, Aneesh wrote: > 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. > Ok. Thanks. > > > > 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. > Yes, on AM335x the EMIF happens to be in peripheral domain, which in the lowest power mode loses its settings. So, while suspending, we save the various EMIF parameters with the help of some assembly code that is running from the internal RAM. During resume, we just store the settings and jump back to SDRAM. Since the header that you are adding is coming from the h/w database I guess it makes more sense to reuse that. Regards, Vaibhav ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-02-09 14:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <331ABD5ECB02734CA317220B2BBEABC1317897B8@DBDE01.ent.ti.com>
2012-02-09 11:25 ` [RFC PATCH 3/8] misc: emif: add register definitions for EMIF Bedia, Vaibhav
2012-02-09 14:20 ` Aneesh V
2012-02-09 14:44 ` Bedia, Vaibhav
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox