Hello Teerth, On Thu, 21 Jan 2010, Reddy, Teerth wrote: > > -----Original Message----- > > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > > Sent: Thursday, January 21, 2010 11:05 AM > > To: Reddy, Teerth > > Cc: Kevin Hilman; linux-omap@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH] OMAP3: PM: Dynamic calculation of SDRC clock > > stabilization delay > > > > Hi Teerth, > > > > any update on Kevin's comments? > > > > This patch shouldn't use a hardcoded value. Please explain further why > > that formula can't be included... > > Time required to switch clocks - 4 REFCLKS + 2 CLKOUTX2 Gives a small > number which doesn't seem to work and causes instability during DVFS. I > found that the value of 6us is safe and stable for the DVFS.I tried this > value on OMAP3430 sdp, zoom2 and zoom3 and it worked fine. I will let > you know more about the formula once I get the updates. Any update on this? Still waiting. I don't see any reason why this formula couldn't be encoded. If you can't get your implementation of the formula to work, please post the code for us to examine. 6 microseconds is definitely too long for some cases and too short for others, so hardcoding that value is not correct. - Paul -- 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