public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: ambresh <a0393775@ti.com>
To: "Sripathy, Vishwanath" <vishwanath.bs@ti.com>
Cc: "K, Ambresh" <ambresh@ti.com>, "Gurav ,
	Pramod" <pramod.gurav@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] OMAP3630 SDRC: Change in DVFS Latency Formula for OMAP3630
Date: Tue, 23 Mar 2010 08:19:05 +0530	[thread overview]
Message-ID: <4BA82C21.4010209@ti.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608703045F2FF1@dbde02.ent.ti.com>

Sripathy, Vishwanath wrote:

>>>
>> -PFA,
>>
>> - Attached patch provides further optimized 3630 & 3430 path for
>> calculating M2 stablization delay.
>>
>> - The formula used to compute clkoutx2, is actually calculating for
>> clkoutm2x2 according to trm  clkoutx2 = (Fref * 2 * M)/ (N + 1).
>>   (Thanks to Eduardo for pointing this).
>>
> No, CLKOUTX2 is dependent on M2. Pls refer to table 3-45 (DPLL Operating Mode and Latency) in 3630 TRM Version D. 
> 

Yes! Stabilization delay for CLKOUTx2 is dependent on M2.

Confusion prevailed because of the section 3.5.3.3.3.1 where clkoutx2 is 
not dependent on M2 factor. And moreover the formula used to calculate 
clkoutx2 in this case looks like the one used for computing clkout_M2X2 :)

Thanks,
Ambresh

  reply	other threads:[~2010-03-23  2:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  4:55 [PATCH 0/2] OMAP3: Dynamic Calculation of SDRC stall latency during DVFS Pramod Gurav
2010-03-18  4:55 ` [PATCH v4 1/2] OMAP3: SDRC: " Pramod Gurav
2010-03-18  4:55   ` [PATCH v2 2/2] OMAP3630 SDRC: Change in DVFS Latency Formula for OMAP3630 Pramod Gurav
2010-03-18  7:17     ` ambresh
2010-03-19 13:17       ` Sripathy, Vishwanath
2010-03-23  2:49         ` ambresh [this message]
2010-03-18  6:17   ` [PATCH v4 1/2] OMAP3: SDRC: Dynamic Calculation of SDRC stall latency during DVFS G, Manjunath Kondaiah
2010-03-18 14:48     ` Kevin Hilman
2010-03-18  7:15   ` ambresh
2010-03-19 13:15     ` Sripathy, Vishwanath
2010-03-21 13:24       ` ambresh
2010-03-18 15:09   ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA82C21.4010209@ti.com \
    --to=a0393775@ti.com \
    --cc=ambresh@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=pramod.gurav@ti.com \
    --cc=vishwanath.bs@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox