> -----Original Message----- > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > ow...@vger.kernel.org] On Behalf Of Nishanth Menon > Sent: Wednesday, December 01, 2010 8:09 PM > To: TAO HU > Cc: TAO HU; linux-omap; Jean; Tony; Kevin; Vishwa > Subject: Re: [PATCH 4/5 v2] OMAP3630: PM: Disable L2 cache while > invalidating L2 cache > > TAO HU had written, on 12/01/2010 02:56 AM, the following: > > Do we need to implement the same thing in bootloader? > > I.e. Do we need to disable L2 prior invalidating L2 for OMAP3630 1st > boot up? > Though out of context for this email list (linux kernel :)), I believe > it wont hurt to do this as a standard procedure.
You should always invalidate the cache before enabling it. Now if at the 1st boot-up if the ROM code / boot-loader is doing this, you don't have do it. At least from kernel point of it's responsibility of boot-loaders/boot-straps to keep the caches invalidated. That's why the generic kernel don't invalidate them before enabling them. RMK has documeneted this. Read " 2. Loader Checks" http://www.arm.linux.org.uk/developer/noboot-checklist/ Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
