From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Davinci: davinci_nand.c performance enhancments
Date: Wed, 6 Jan 2010 16:13:22 -0600 [thread overview]
Message-ID: <20100106221322.GA28859@loki.buserror.net> (raw)
In-Reply-To: <4B28C16E.8060604@ge.com>
On Wed, Dec 16, 2009 at 11:15:58AM +0000, Nick Thompson wrote:
> Introduces various optimisations that approximately triple the
> read data rate from NAND when run on da830evm.
>
> Most of these optimisations depend on the endianess of the machine
> and most of them are very similar to optimisations already present
> in the Linux Kernel.
>
> Signed-off-by: Nick Thompson <nick.thompson@ge.com>
> ---
> Changes:
> Cleaned up based on Scott Wood's comments:
> read/write_buf slightly faster and catches more cases.
> Removed unnecessary and/or badly named variables.
>
> drivers/mtd/nand/davinci_nand.c | 200 ++++++++++++++++++++++++++++-----------
> 1 files changed, 146 insertions(+), 54 deletions(-)
Applied to u-boot-nand-flash.
-Scott
prev parent reply other threads:[~2010-01-06 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 11:15 [U-Boot] [PATCH v2] Davinci: davinci_nand.c performance enhancments Nick Thompson
2010-01-06 22:13 ` Scott Wood [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=20100106221322.GA28859@loki.buserror.net \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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.