From: Joe Perches <joe@perches.com>
To: Holger Schurig <holgerschurig@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Sujith Manoharan <sujith@msujith.org>,
ath9k-devel <ath9k-devel@lists.ath9k.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: [PATCH] checkpatch: Add test for long udelay
Date: Tue, 04 Feb 2014 04:59:25 -0800 [thread overview]
Message-ID: <1391518765.2538.18.camel@joe-AO722> (raw)
In-Reply-To: <CAOpc7mFQZ3efZda0cC28BLATqRDJ99BRNu=ezQq8wa+dyFyOvA@mail.gmail.com>
On Tue, 2014-02-04 at 08:03 +0100, Holger Schurig wrote:
> The macro udelay
> cannot handle large values because of lost-of-precision.
>
> IMHO udelay on ARM is broken, because it also cannot work with fast
> ARM processors (where bogomips >= 3355, which is in sight now). It's
> just not broken enought that someone did something against it ... so
> the current kludge is good enought.
Until then, warn on long udelay uses.
Also fix uses of $line that should have been $herecurr.
Signed-off-by: Joe Perches <joe@perches.com>
---
scripts/checkpatch.pl | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 0ea2a1e..36275c5 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3912,10 +3912,15 @@ sub process {
# prefer usleep_range over udelay
if ($line =~ /\budelay\s*\(\s*(\d+)\s*\)/) {
+ my $delay = $1;
# ignore udelay's < 10, however
- if (! ($1 < 10) ) {
+ if (! ($delay < 10) ) {
CHK("USLEEP_RANGE",
- "usleep_range is preferred over udelay; see Documentation/timers/timers-howto.txt\n" . $line);
+ "usleep_range is preferred over udelay; see Documentation/timers/timers-howto.txt\n" . $herecurr);
+ }
+ if ($delay > 2000) {
+ WARN("LONG_UDELAY",
+ "long udelay - prefer mdelay; see arch/arm/include/asm/delay.h\n" . $herecurr);
}
}
@@ -3923,7 +3928,7 @@ sub process {
if ($line =~ /\bmsleep\s*\((\d+)\);/) {
if ($1 < 20) {
WARN("MSLEEP",
- "msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt\n" . $line);
+ "msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt\n" . $herecurr);
}
}
next prev parent reply other threads:[~2014-02-04 12:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 3:07 [PATCH 0/3] ath9k patches Sujith Manoharan
2014-02-04 3:07 ` [PATCH 1/3] ath9k: Fix build error on ARM Sujith Manoharan
2014-02-04 3:34 ` Joe Perches
2014-02-04 3:40 ` Sujith Manoharan
2014-02-04 7:03 ` [ath9k-devel] " Holger Schurig
2014-02-04 12:59 ` Joe Perches [this message]
2014-02-04 16:36 ` Joe Perches
2014-02-04 18:40 ` Arnd Bergmann
2014-02-04 19:43 ` Joe Perches
2014-02-05 11:50 ` Russell King - ARM Linux
2014-02-05 12:32 ` Joe Perches
2014-02-05 12:41 ` Russell King - ARM Linux
2014-02-05 13:04 ` Joe Perches
2014-02-05 13:39 ` Russell King - ARM Linux
2014-02-05 14:03 ` Joe Perches
2014-02-05 14:21 ` Russell King - ARM Linux
2014-02-05 15:05 ` Joe Perches
2014-02-04 3:07 ` [PATCH 2/3] ath9k: Do not support PowerSave by default Sujith Manoharan
2014-02-04 3:07 ` [PATCH 3/3] ath9k: Fix TX power calculation Sujith Manoharan
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=1391518765.2538.18.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=holgerschurig@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sujith@msujith.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