From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v2] [SCSI] atp870u: Fix bad use of udelay
Date: Tue, 24 Apr 2012 14:18:50 -0700 [thread overview]
Message-ID: <20120424141850.e5cdf6c2.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120424074916.GA25261@burratino>
On Tue, 24 Apr 2012 02:49:16 -0500
Jonathan Nieder <jrnieder@gmail.com> wrote:
> From: Martin Michlmayr <tbm@cyrius.com>
>
> The ACARD driver calls udelay() with a value > 2000, which leads to
> to the following compilation error on ARM:
> ERROR: "__bad_udelay" [drivers/scsi/atp870u.ko] undefined!
> make[1]: *** [__modpost] Error 1
>
> ...
>
> --- a/drivers/scsi/atp870u.c
> +++ b/drivers/scsi/atp870u.c
> @@ -1173,7 +1173,16 @@ wait_io1:
> outw(val, tmport);
> outb(2, 0x80);
> TCM_SYNC:
> - udelay(0x800);
> + /*
> + * The funny division into multiple delays is to accomodate
> + * arches like ARM where udelay() multiplies its argument by
> + * a large number to initialize a loop counter. To avoid
> + * overflow, the maximum supported udelay is 2000 microseconds.
> + *
> + * XXX it would be more polite to find a way to use msleep()
> + */
> + mdelay(2);
> + udelay(48);
> if ((inb(tmport) & 0x80) == 0x00) { /* bsy ? */
> outw(0, tmport--);
> outb(0, tmport);
Fair enough, I say. Looking at this driver, I do think it's best to
minimally fix the build and then tiptoe away very delicately lest
something explode.
That being said, I'm glad the kernel has a function called "fun_scam".
prev parent reply other threads:[~2012-04-24 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901092028.n09KSAeI024551@imap1.linux-foundation.org>
[not found] ` <20090109205835.GB5069@deprecation.cyrius.com>
[not found] ` <20090109130308.bfde281e.akpm@linux-foundation.org>
[not found] ` <1231536107.3235.50.camel@localhost.localdomain>
2012-04-24 7:49 ` [PATCH/RFC v2] [SCSI] atp870u: Fix bad use of udelay Jonathan Nieder
2012-04-24 21:18 ` Andrew Morton [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=20120424141850.e5cdf6c2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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).