From: Jonathan McDowell <noodles@earth.li>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH/RFC] Add Amstrad Delta NAND support.
Date: Tue, 25 Apr 2006 15:03:11 +0100 [thread overview]
Message-ID: <20060425140311.GP7570@earth.li> (raw)
In-Reply-To: <1145972592.11909.392.camel@pmac.infradead.org>
On Tue, Apr 25, 2006 at 02:43:12PM +0100, David Woodhouse wrote:
> On Mon, 2006-04-24 at 17:15 +0100, Jonathan McDowell wrote:
> > In particular I'm using "udelay(1);" in the read/write routines to wait
> > for the bus to settle after setting the read/write enable lines. Really
> > I want "ndelay(40);", but ndelay doesn't seem to be implemented on ARM,
> > except in terms of udelay. Can I get away with udelay(0.04)? Should I be
> > doing something else entirely?
>
> That's a question best directed at linux-arm-kernel list.
Ok, ta.
> > +/*
> > + * These 3 functions are basically identical to the ones in nand_base.c, but
> > + * we have to call our read_byte/write_byte functions instead of readb/writeb
> > + * directly. I submitted a patch to MTD to move this to nand_base.c, but it
> > + * was deemed too intrusive.
> > + */
>
> Thomas' decision, I assume? I think he's right -- this way it can be
> inlined in the loop rather than being a real function call for every
> byte.
Ben Dooks. I'd actually forgotten I'd left that comment in. I'll remove
it before I submit the patch proper; it was mainly a note to people who
might have picked up my earlier version that patches nand-core as well.
J.
--
/-\ | What's the worse that could
|@/ Debian GNU/Linux Developer | happen? Smoke. - Anonymous
\- | HWHacker
next prev parent reply other threads:[~2006-04-25 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 16:15 [PATCH/RFC] Add Amstrad Delta NAND support Jonathan McDowell
2006-04-25 13:43 ` David Woodhouse
2006-04-25 13:48 ` Jörn Engel
2006-04-25 13:58 ` David Woodhouse
2006-04-25 14:05 ` Jörn Engel
2006-04-25 14:03 ` Jonathan McDowell [this message]
2006-05-14 2:45 ` 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=20060425140311.GP7570@earth.li \
--to=noodles@earth.li \
--cc=dwmw2@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox