>>-----Original Message----- >>From: Paul Walmsley [mailto:[email protected]] >>Sent: Wednesday, January 06, 2010 6:02 AM >>To: Gopinath, Thara >>Cc: [email protected] >>Subject: RE: [PATCH] OMAP3: hwmod: Adding flag to prevent caching of >>sysconfig register. >> >>On Wed, 23 Dec 2009, Gopinath, Thara wrote: >> >>> Hi Paul,Kevin.. Does this patch look ok? >> >>Hello Thara, >> >>looking over this patch. Nice job on the descriptive patch comment; >>it explains the problem well. What do you think about a slightly >>different approach -- that is, to add a hook to the hwmod code to >>invalidate the cache if the module's powerdomain has lost context?
Hi Paul It should be possible but I feel it is a bit cumbersome. Couple of reasons I have. a. Some modules like smartreflex does not have any power domain associated with it. b. Invalidating the cache is not needed for all modules even if the module powerdomain context is lost. This is needed only for modules which employ always restore mechanism. All other modules will do explicit context save and restore of its registers c. Getting whether power domain context is lost or not is not very straight forward. If I am not mistaken the only way is to keep tab of the powerdomain counters through omap_pm_get_dev_context_loss_count. I might be mistaken. Regards Thara -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
