From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Huang Shijie <shijie8@gmail.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Roy Lee <roylee@paypal.com>,
Mike Voytovich <mvoytovich@paypal.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/3] mtd: nand: gpmi: add proper raw access support
Date: Sun, 30 Nov 2014 00:46:27 -0800 [thread overview]
Message-ID: <20141130084627.GD3608@norris-Latitude-E6410> (raw)
In-Reply-To: <1417020793-3354-1-git-send-email-boris.brezillon@free-electrons.com>
On Wed, Nov 26, 2014 at 05:53:10PM +0100, Boris Brezillon wrote:
> This series provides an implementation for raw accesses taking care of
> hidding the specific layout used by the GPMI controller.
>
> Best Regards,
>
> Boris
>
> Changes since v4:
> - fixed a few corner cases in gpmi_move_bits (tested it with:
> https://github.com/bbrezillon/gpmi-move-bits-test/blob/master/gpmi-move-bits-test.c)
Thanks for this.
BTW, I was going to ask if you benchmarked the much simpler
simple_move_bits() version against the more complicated version here,
but I just ran it myself; the simple version performed about 10x slower
when testing on my PC. So I guess that can justify some extra
complexity!
> - add documentation and comments for the new gpmi functions
>
> Changes since v3:
> - add comments to the gpmi_move_bits function
> - extend raw read/write documentation
> - move last part of the raw_page_read function into a conditional block
>
> Changes since v2:
> - fixed a bug in gpmi_move_bits
> - add a raw_buffer field to be used when using raw access methods
> (experienced memory corruptions when directly using page_buffer_virt
> buffer)
> - add raw OOB access functions
Other than my comment about move vs. copy, I think this looks good
enough.
Brian
prev parent reply other threads:[~2014-11-30 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 16:53 [PATCH v5 0/3] mtd: nand: gpmi: add proper raw access support Boris Brezillon
2014-11-26 16:53 ` [PATCH v5 1/3] mtd: nand: gpmi: add gpmi_move_bits function Boris Brezillon
2014-11-26 16:57 ` Boris Brezillon
2014-11-30 8:11 ` Brian Norris
2014-11-30 8:55 ` Boris Brezillon
2014-11-30 15:39 ` Huang Shijie
2014-11-26 16:53 ` [PATCH v5 2/3] mtd: nand: gpmi: add proper raw access support Boris Brezillon
2014-11-26 16:53 ` [PATCH v5 3/3] mtd: nand: gpmi: add raw oob access functions Boris Brezillon
2014-11-30 8:46 ` Brian Norris [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=20141130084627.GD3608@norris-Latitude-E6410 \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mvoytovich@paypal.com \
--cc=roylee@paypal.com \
--cc=shijie8@gmail.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