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>,
"Reddy, Teerth" <teerth@ti.com>
Subject: Re: [PATCH v4 1/2] OMAP3: SDRC: Dynamic Calculation of SDRC stall latency during DVFS
Date: Sun, 21 Mar 2010 18:54:42 +0530 [thread overview]
Message-ID: <4BA61E1A.8080603@ti.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608703045F2FED@dbde02.ent.ti.com>
Sripathy, Vishwanath wrote:
>
>>> + /* calculate the sram delay */
>>> + delay_sram = (((mpurate / gt_rate) * diff) / (loop * 2));
>>> +
>>> + error_gain = mpurate / gt_rate;
>>> + delay_sram = delay_sram + error_gain;
>> Cosmetic changes:
>>
>> error_gain = mpurate / gt_rate;
>> delay_sram = (error_gain * diff) / (loop);
>> delay_sram += error_gain;
>>
> Why *2 is missing in your code? 2 is needed since the loop takes 2 arm cycles.
its a typo, it should be (loop * 2).
BR,
Ambresh
>
> Regards
> Vishwa
>> Thanks,
>> Ambresh
>>
>>> +
>>> + return delay_sram;
>>> +}
>>> +#endif
>>> +
>>> int __init omap_sram_init(void)
>>> {
>>> omap_detect_sram();
>>> omap_map_sram();
>>>
>>> +#ifdef CONFIG_ARCH_OMAP3
>>> + _omap3_sram_delay = omap_sram_push(__sram_wait_delay,
>>> + __sram_wait_delay_sz);
>>> +#endif
>>> +
>>> if (!(cpu_class_is_omap2()))
>>> omap1_sram_init();
>>> else if (cpu_is_omap242x())
>
next prev parent reply other threads:[~2010-03-21 13:25 UTC|newest]
Thread overview: 13+ 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
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 [this message]
2010-03-18 15:09 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2010-04-01 17:16 [PATCH V4 0/2] OMAP3: " Pramod Gurav
2010-04-01 17:16 ` [PATCH v4 1/2] OMAP3: SDRC: " Pramod Gurav
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=4BA61E1A.8080603@ti.com \
--to=a0393775@ti.com \
--cc=ambresh@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=pramod.gurav@ti.com \
--cc=teerth@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