From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] MTD: atmel_nand: optimize read/write buffer functions
Date: Wed, 06 Jul 2011 09:58:11 +0300 [thread overview]
Message-ID: <1309935496.3149.73.camel@sauron> (raw)
In-Reply-To: <1309789073-14593-1-git-send-email-nicolas.ferre@atmel.com>
On Mon, 2011-07-04 at 16:17 +0200, Nicolas Ferre wrote:
> For PIO NAND access functions, we use the features of the SMC:
> - no need to take into account the NAND bus width: SMC will deal with this
> - use of an IO memcpy on the NAND chip-select space is able to generate
> proper SMC behavior.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> V2: use of memcpy_fromio/memcpy_toio for proper handling of memory types.
Pushed to l2-mtd-2.6.git, thanks!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2011-07-06 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:50 [RFC PATCH] MTD: atmel_nand: optimize read/write buffer functions Nicolas Ferre
2011-06-28 11:10 ` Uwe Kleine-König
2011-06-28 13:58 ` Nicolas Ferre
2011-06-28 14:59 ` Russell King - ARM Linux
2011-06-29 13:09 ` Nicolas Ferre
2011-06-29 13:31 ` Russell King - ARM Linux
2011-07-04 13:02 ` Nicolas Ferre
2011-07-04 14:17 ` [PATCH V2] " Nicolas Ferre
2011-07-06 6:58 ` Artem Bityutskiy [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=1309935496.3149.73.camel@sauron \
--to=dedekind1@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).