From: afzal.mohd.ma@gmail.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: spin one more cycle in timer-based delays
Date: Sat, 19 Nov 2016 12:47:02 +0530 [thread overview]
Message-ID: <20161119071702.GA25647@afzalpc> (raw)
In-Reply-To: <582F0DD2.3030805@free.fr>
Hi Mason,
On Fri, Nov 18, 2016 at 03:18:58PM +0100, Mason wrote:
> On 18/11/2016 13:54, Russell King - ARM Linux wrote:
> > So, NAK on this change. udelay is not super-accurate.
>
> usleep_range() fixed this issue recently.
> 6c5e9059692567740a4ee51530dffe51a4b9584d
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=timers/core&id=6c5e9059692567740a4ee51530dffe51a4b9584d
But the above "timers: Fix usleep_range() in the context of
wake_up_process()" is to avoid wakeup causing premature return than
about being precise, no ?
With conflicting opinion on delay/sleep fn's from the players, the one
in gallery would get confused.
But Linus has mentioned udelay as not meant to be precise, okay ?
Regards
afzal
next prev parent reply other threads:[~2016-11-19 7:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 13:36 [PATCH] arm: spin one more cycle in timer-based delays Mason
2016-11-18 12:06 ` Will Deacon
2016-11-18 12:24 ` Mason
2016-11-18 12:54 ` Russell King - ARM Linux
2016-11-18 14:18 ` Mason
2016-11-18 14:42 ` Peter Zijlstra
2016-11-18 17:51 ` Mason
2016-11-19 7:17 ` Afzal Mohammed [this message]
2016-11-19 11:03 ` Russell King - ARM Linux
2016-11-19 18:29 ` Mason
2016-11-20 19:18 ` Doug Anderson
2016-11-20 19:44 ` Russell King - ARM Linux
2016-11-20 20:00 ` Mason
2016-11-20 6:15 ` Afzal Mohammed
2016-11-20 19:15 ` Doug Anderson
2016-11-18 17:13 ` Doug Anderson
2016-11-18 17:32 ` Russell King - ARM Linux
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=20161119071702.GA25647@afzalpc \
--to=afzal.mohd.ma@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).