From: saquib.herman@gmail.com (Saquib)
To: linux-arm-kernel@lists.infradead.org
Subject: Duration of mdelay and udelay depends on MPU frequency in SMP
Date: Thu, 5 May 2011 12:23:31 +0530 [thread overview]
Message-ID: <BANLkTimVPnzMCL=NMb7hDkL97nJ=XdFExw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikGXzLba8uqXoffaUixBrEGj-XzRQ@mail.gmail.com>
Hi All,
Can anyone please help me to understand and fix this issue?
When CPU frequency is "1008MHz", duration of delay was close to theoretical
value, however, when "300MHz", it was close to about 4 times the theoretical
value.
I tested it on OMAP4(SMP) blaze board.
--
Thanks & regards,
Saquib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110505/87732fff/attachment-0001.html>
next prev parent reply other threads:[~2011-05-05 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 6:49 Duration of mdelay and udelay depends on MPU frequency in SMP Saquib
2011-05-05 6:53 ` Saquib [this message]
2011-05-12 6:42 ` Santosh Shilimkar
2011-06-10 22:19 ` Menon, Nishanth
2011-06-14 3:24 ` Stephen Boyd
2011-06-14 4:19 ` Menon, Nishanth
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='BANLkTimVPnzMCL=NMb7hDkL97nJ=XdFExw@mail.gmail.com' \
--to=saquib.herman@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).