mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "vimal singh" <vimalsingh@ti.com>
To: linux-mtd@lists.infradead.org
Cc: "Tony Lindgren" <tony@atomide.com>,
	dwmw2@infradead.org, dedekind@infradead.org, david-b@pacbell.net,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCH 0/2] [MTD] [NAND] Add prefetch and dma support for omap2/3   NAND      driver
Date: Fri, 10 Jul 2009 17:06:50 +0530 (IST)	[thread overview]
Message-ID: <52588.192.168.10.89.1247225810.squirrel@dbdmail.itg.ti.com> (raw)
In-Reply-To: <47286.192.168.10.89.1244108024.squirrel@dbdmail.itg.ti.com>

Hi,

I have splited gpmc prefetch support for NAND into two patches:
[PATCH 1:2] : Adding support for nand prefetch-read and post-write, in MPU mode.
[PATCH 2:2] : Adding DMA mode support in nand prefetch/post-write

These patches implements Tony's comments. (For comments and discussion see:
http://lists.infradead.org/pipermail/linux-mtd/2009-June/025993.html)

Other than that, gpmc_prefetch_(inti/request) call has been removed, as nothing
great was done in that and we really do not need that.

Function 'gpmc_prefetch_enable' does check for 'if prefetch is already being
used by some other driver?'. And if it is busy, normal cpu copy method for
read/write request will be used.

Thanks and regards,
vimal





      parent reply	other threads:[~2009-07-10 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54851.192.168.10.89.1243946277.squirrel@dbdmail.itg.ti.com>
2009-06-04  9:33 ` [PATCH] " vimal singh
2009-06-04 15:28   ` Tony Lindgren
2009-06-05 12:00     ` Singh, Vimal
2009-06-08 11:38       ` Tony Lindgren
2009-06-08 16:01         ` Singh, Vimal
2009-06-09 10:19           ` Tony Lindgren
2009-06-09 15:24             ` Singh, Vimal
2009-06-09 15:57               ` Tony Lindgren
     [not found] ` <47286.192.168.10.89.1244108024.squirrel@dbdmail.itg.ti.com>
2009-07-10 11:36   ` vimal singh [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=52588.192.168.10.89.1247225810.squirrel@dbdmail.itg.ti.com \
    --to=vimalsingh@ti.com \
    --cc=david-b@pacbell.net \
    --cc=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®