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@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of V, Aneesh > >> Sent: Saturday, February 04, 2012 5:46 PM > >> To: linux-omap@xxxxxxxxxxxxxxx > >> Cc: linux-kernel@xxxxxxxxxxxxxxx; akpm@xxxxxxxxxxxxxxxxxxxx; 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
