From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug: loops_per_jiffy based udelay() mostly shorter than requested
Date: Wed, 12 Jan 2011 22:23:37 +0000 [thread overview]
Message-ID: <20110112222337.GK11039@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTik5BmZAOFdYVGAjuoHftQ3qh1oTCEr5MpkCiDVz@mail.gmail.com>
On Wed, Jan 12, 2011 at 01:19:49PM -0800, Linus Torvalds wrote:
> On Sun, Jan 9, 2011 at 9:08 AM, Russell King <rmk@arm.linux.org.uk> wrote:
> >
> > Any suggestions or thoughts, or should we not care too much if udelay()
> > produces slightly shorter than desired delays? ?Or am I doing something
> > horribly wrong in the ARM code?
>
> Judging by the numbers you quote, I would definitely put this in the
> "don't care too much".
Thanks - that's my thoughts too. I think I'm still going to push out
the rounding patch for the sake of correctness even though it's down
in the noise.
prev parent reply other threads:[~2011-01-12 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 17:08 Bug: loops_per_jiffy based udelay() mostly shorter than requested Russell King
2011-01-12 21:19 ` Linus Torvalds
2011-01-12 22:23 ` Russell King - ARM Linux [this message]
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=20110112222337.GK11039@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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