public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.27-rc3-omap1] omap2_nand updates
Date: Mon, 1 Sep 2008 00:54:08 +0300	[thread overview]
Message-ID: <20080831215405.GM9887@frodo> (raw)
In-Reply-To: <200808311419.05598.david-b@pacbell.net>

On Sun, Aug 31, 2008 at 02:19:05PM -0700, David Brownell wrote:
> From: David Brownell <dbrownell@users.sourceforge.net>
> 
> Minor updates to the OMAP{2,3} NAND driver:
> 
>  - Rename those buffer PIO routines as *_buf16()
>  - Get rid of pointless LE16 data conversions; OMAP is always LE
>  - Speed up buffer reads by switching to __raw_readsl()
> 
> Right now this driver only handles 16-bit NAND, but eventually it
> should handle 8-bit too.  Moreover it may be worth using DMA...
> 
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>

Thanks Dave, I'll melded it up in my queue.

-- 
balbi

  reply	other threads:[~2008-08-31 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31 21:19 [patch 2.6.27-rc3-omap1] omap2_nand updates David Brownell
2008-08-31 21:54 ` Felipe Balbi [this message]
2008-09-09  1:02   ` Tony Lindgren

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=20080831215405.GM9887@frodo \
    --to=me@felipebalbi.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.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