> -----Original Message----- > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > ow...@vger.kernel.org] On Behalf Of Cousson, Benoit > Sent: Monday, March 07, 2011 7:21 PM > To: Valkeinen, Tomi; Nayak, Rajendra > Cc: Paul Walmsley; Hilman, Kevin; linux-omap; Taneja, Archit; > Semwal, Sumit > Subject: Re: Problem with DSS clocks & accessing registers > > + Rajendra > > Hi Tomi, > > On 3/7/2011 9:22 AM, Valkeinen, Tomi wrote: > > Hi Kevin, Paul, > > > > We currently have a small problem with OMAP4 DSS. When we enable > the DSS > > clocks, it seems that the DSS registers are not always accessible > right > > after the clock enable. > > What clocks are you talking about? As you know, the DSS has a bunch > of functional clocks available depending of the use case. > > > I understood that on OMAP4 the clock framework doesn't guarantee > that > > the registers are accessible after enabling clocks, and pm_runtime > will handle this. Is this correct? >
This seems to the question about a so called optional clock (DSS_CLK) which really not an optional clock :) This clock needs to be enabled and disabled along with interface and functional clock for the registers access to work. If you look internals of the clock routing in DSS, Figure 10-4 this clock is not really optional. You can call it optional because there can be a option to use PLL clock instead of this one. But the fact is either DSS_CLK or the PLL clock has to be running for the IP accesses to work. Sumit, Please add more points about our discussion on this one. 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
