All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
	Martin Michlmayr <tbm@cyrius.com>,
	linux-scsi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [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".

WARNING: multiple messages have this Message-ID (diff)
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".

  reply	other threads:[~2012-04-24 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 20:28 [patch 10/11] scsi: fix bad use of udelay in atp870u.c akpm
2009-01-09 20:58 ` Martin Michlmayr
2009-01-09 21:03   ` Andrew Morton
2009-01-09 21:21     ` James Bottomley
2009-01-10 15:50       ` Christoph Hellwig
2012-04-24  7:49       ` [PATCH/RFC v2] [SCSI] atp870u: Fix bad use of udelay Jonathan Nieder
2012-04-24  7:49         ` Jonathan Nieder
2012-04-24 21:18         ` Andrew Morton [this message]
2012-04-24 21:18           ` Andrew Morton

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=JBottomley@parallels.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tbm@cyrius.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.