linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [Openpxa-users] Linux udelay() is way off
Date: Thu, 20 Jan 2011 18:00:04 +0100	[thread overview]
Message-ID: <201101201800.04289.marek.vasut@gmail.com> (raw)
In-Reply-To: <AANLkTin_cCzNWhJnD=A2h1qiKpeUrnPrSZPs_Kmfjjd1@mail.gmail.com>

On Thursday 20 January 2011 17:09:00 Bj?rn Forsman wrote:
> Hi,
> 
> On my Colibri PXA310, I see that Linux udelay() is only 30 % of the
> length it's supposed to. This is way off and cause problems (e.g.
> 1-Wire device driver breaks). I'm running OpenPXA bootloaders (OBM2 +
> U-Boot) and mainline Linux 2.6.36.
> 
> Any ideas how to fix this?
> 
> Could it be that U-Boot sets up the system clock to something
> different than what Linux "expects" so that loops_per_jiffy becomes
> wrong? I see some clock setup in <u-boot-pxa>/arch/arm/cpu/pxa/start.S
> but I'm not sure what to do with it (yet). I'd like to try out
> different clock speeds to see if it helps. Any pointers?
> 
> I also have a workaround in mind: Try out different lpj= settings on
> the kernel command line until a udelay(1000) actually is 1000 us. Is
> this a sane thing to do?

CCing relevant people.

And no, linux kernel should derive it's timing properly so it's a kernel bug.

Cheers
> 
> Best regards,
> Bj?rn Forsman
> 
> ---------------------------------------------------------------------------
> --- Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Openpxa-users mailing list
> Openpxa-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openpxa-users

       reply	other threads:[~2011-01-20 17:00 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 ` Marek Vasut [this message]
2011-01-20 17:55   ` [Openpxa-users] Linux udelay() is way off 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
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=201101201800.04289.marek.vasut@gmail.com \
    --to=marek.vasut@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).