public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [REPOST] mtd: extend plat_nand for (read|write)_buf
Date: Fri, 15 May 2009 16:05:49 +0100	[thread overview]
Message-ID: <20090515150549.GE32684@woodchuck> (raw)
In-Reply-To: <1242395460.27996.249.camel@localhost.localdomain>

Hi,

* Artem Bityutskiy <dedekind@infradead.org> [2009-05-15 16:51:00+0300]:
> 
> On Mon, 2009-05-11 at 19:28 +0100, Alexander Clouter wrote:
> > This patch adds (write|read)_buf callbacks to plat_nand.
> > 
> > The NAND on the TS-7800 provisioned by the FPGA allows readw() and 
> > readl() to be used which gives a 2.5x speed up.  To be able to use this 
> > from the plat_nand driver a hook for read_buf (and also write_buf whilst 
> > we are in there) need to be made available.  This patch adds the hook.
> > 
> > This is a repost[1] of a feature asked for before[2], plus other helpful 
> > patches to plat_nand[3] would be welcomed if at all possible too.
> > 
> > [1] http://lists.infradead.org/pipermail/linux-mtd/2009-March/024747.html
> > [2] http://lists.infradead.org/pipermail/linux-mtd/2007-October/019659.html
> > [3] http://lists.infradead.org/pipermail/linux-mtd/2009-March/024780.html
> > 
> > Signed-off-by: Alexander Clouter <alex@digriz.org.uk>
> 
> I think this should be submitted with the user at the same
> time. Adding hooks without having a user is not very good.
> E.g., you may find out later that this does not help, or
> cancel your project, or end up with different call-backs,
> etc.
> 
In the case of read/write_buf...there is no other way, I'm all ears if 
you know how I can do (read|write)(w|l) with plat_nand *now*?

I just pulled off this type of manoeuvre for a HW RNG driver:

http://lkml.indiana.edu/hypermail/linux/kernel/0902.2/02727.html
http://git.marvell.com/?p=orion.git;a=commit;h=8be7b57dea0467324ad4545334c5e35c18f0814b

I doubt the ARM people would be happy if I push ARM patches through the 
MTD sub-system :)

> You may keep this patch privately, work on your NAND driver,
> and when you have it ready, you submit it with this at the
> same time.
> 
Erm, it's been ready for a *long* time, about a year[1], and is being 
used.  Recently the bits of my plat_nand impementation[2] is on it's way 
to going mainline (Orion -> ARM -> Linus):

http://git.marvell.com/?p=orion.git;a=commit;h=75bb6b9aab3255f440ef4e72a31978d1681105d6

Cheers

[1] http://tech.groups.yahoo.com/group/ts-7000/message/11616
[2] http://lists.infradead.org/pipermail/linux-mtd/2009-February/024555.html

-- 
Alexander Clouter
.sigmonster says: Your fly might be open (but don't check it just now).

  reply	other threads:[~2009-05-15 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 18:28 [PATCH] [REPOST] mtd: extend plat_nand for (read|write)_buf Alexander Clouter
2009-05-15 13:51 ` Artem Bityutskiy
2009-05-15 15:05   ` Alexander Clouter [this message]
2009-05-15 15:27     ` Alexander Clouter
2009-05-15 15:31     ` Artem Bityutskiy

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=20090515150549.GE32684@woodchuck \
    --to=alex@digriz.org.uk \
    --cc=dedekind@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