All of lore.kernel.org
 help / color / mirror / Atom feed
From: bjorn.forsman@gmail.com (Bjørn Forsman)
To: linux-arm-kernel@lists.infradead.org
Subject: [Openpxa-users] Linux udelay() is way off
Date: Fri, 21 Jan 2011 18:46:48 +0100	[thread overview]
Message-ID: <AANLkTi=cwRNCxS6qbR3Kp2Sf-ckx+wcUAgTc8LOYES9F@mail.gmail.com> (raw)
In-Reply-To: <20110120193013.GL6335@n2100.arm.linux.org.uk>

2011/1/20 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> On Thu, Jan 20, 2011 at 08:18:10PM +0100, Bj?rn Forsman wrote:
>> [ ? 11.425363] cpufreq-core: saving 518144 as reference value for
>> loops_per_jiffy; freq is 312000 kHz
>> [ ? 11.425523] cpufreq-core: scaling loops_per_jiffy to 1036288 for
>> frequency 624000 kHz

[snip]

> Is it possible to boot at 624MHz and report the resulting lpj?
> Alternatively, call calibrate_delay() after the cpufreq switch to
> 624MHz, disabling the 'printed' stuff and see what it reports.

Now I have an extra calibrate_delay() after cpufreq changes the frequency.

First call:
Calibrating delay loop... 103.62 BogoMIPS (lpj=518144)

Second call:
Calibrating delay loop... 622.59 BogoMIPS (lpj=3112960)

(udelay() is correct when having that second call.)

It seems cpufreq thinks it transitions from 312 to 624 MHz, but in
reality it may be transitioning from 104 to 624 MHz (because it now
runs 6 times as fast according to lpj). This may explain the udelay()
error ratio (~0.32):

  104 MHz / 312 MHz = 0.3333..

I think this means either the clock speed or the jiffies interval do
not match what the kernel thinks.

I also did some tests changing the clock speed in the bootloader. It
seems like the only thing that works for the kernel is booting with a
104 MHz clock. Any other frequency and cpufreq will do bad things to
udelay().

Any thoughts?

BTW, I failed at locating the jiffies implementation for PXA310. Any pointers?

Best regards,
Bj?rn Forsman

  parent reply	other threads:[~2011-01-21 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTin_cCzNWhJnD=A2h1qiKpeUrnPrSZPs_Kmfjjd1@mail.gmail.com>
2011-01-20 17:00 ` [Openpxa-users] Linux udelay() is way off Marek Vasut
2011-01-20 17:55   ` Russell King - ARM Linux
2011-01-20 19:18     ` Bjørn Forsman
2011-01-20 19:30       ` Russell King - ARM Linux
2011-01-20 20:25         ` Bjørn Forsman
2011-01-20 22:10           ` Russell King - ARM Linux
2011-01-21  0:02             ` Bjørn Forsman
2011-01-21 17:46         ` Bjørn Forsman [this message]
2011-01-21 18:11           ` Marek Vasut
2011-01-21 18:55             ` Bjørn Forsman
2011-01-23 10:35           ` Marek Vasut
2011-01-25 17:45             ` Bjørn Forsman
2011-01-25 20:18               ` Marek Vasut
2011-01-21  7:29       ` Saravana Kannan
2011-01-21 17:56         ` Bjørn Forsman

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='AANLkTi=cwRNCxS6qbR3Kp2Sf-ckx+wcUAgTc8LOYES9F@mail.gmail.com' \
    --to=bjorn.forsman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.