All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan McDowell <noodles@earth.li>
To: David Vrabel <dvrabel@arcom.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add Amstrad Delta NAND support.
Date: Fri, 19 May 2006 11:01:05 +0100	[thread overview]
Message-ID: <20060519100105.GF7570@earth.li> (raw)
In-Reply-To: <446D90B5.2090802@arcom.com>

On Fri, May 19, 2006 at 10:32:37AM +0100, David Vrabel wrote:
> Jonathan McDowell wrote:
> > On Thu, May 18, 2006 at 06:57:28PM +0200, Jörn Engel wrote:
> >> On Thu, 18 May 2006 17:09:41 +0100, Jonathan McDowell wrote:
> >>> +	omap_writew(0, (OMAP_MPUIO_BASE + OMAP_MPUIO_IO_CNTL));
> >>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> Could that be done in a macro?
> > 
> > Is there any benefit to doing so?
> > 
> >>> +	udelay(0.04);
> >> Floating point in the kernel?
> > 
> > Not quite. udelay is a macro on ARM so this ends up as an integer before
> > it ever hits a function call. In an ideal world I'd use "ndelay(40);"
> > but that would result in a delay of over 1µs as ARM doesn't have ndelay
> > defined so we hit the generic fallback.
> 
> Use instead:
> 
> /* delay for at least 40 ns */
> udelay(1);

Using "ndelay(40);" here would seem to make more sense; it's equivalent
at present and means that once I or someone else provided an ndelay
implementation for ARM the driver wouldn't need changed to take
advantage of it.

J.

-- 
                 /------------------------------------\
                 |      Ships log... erm... one.      |
                 | http://www.blackcatnetworks.co.uk/ |
                 \------------------------------------/

  reply	other threads:[~2006-05-19 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 16:09 [PATCH] Add Amstrad Delta NAND support Jonathan McDowell
2006-05-18 16:57 ` Jörn Engel
2006-05-19  9:01   ` Jonathan McDowell
2006-05-19  9:32     ` David Vrabel
2006-05-19  9:32       ` David Vrabel
2006-05-19 10:01       ` Jonathan McDowell [this message]
2006-05-19 10:03     ` Jörn Engel
2006-05-19 10:26       ` David Woodhouse
2006-05-20  0:10         ` Segher Boessenkool
2006-05-20  0:10           ` Segher Boessenkool
2006-05-19 22:20 ` Jonathan McDowell
2006-05-20 14:10 ` Jonathan McDowell
2006-05-21 17:12   ` David Woodhouse

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=20060519100105.GF7570@earth.li \
    --to=noodles@earth.li \
    --cc=dvrabel@arcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@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 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.