From: Pekon Gupta <pekon@ti.com>
To: <computersforpeace@gmail.com>, <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org, Pekon Gupta <pekon@ti.com>, balbi@ti.com
Subject: [PATCH v3 0/4] optimize and clean-up of OMAP NAND and ELM driver
Date: Sat, 2 Nov 2013 15:16:12 +0530 [thread overview]
Message-ID: <1383385576-26095-1-git-send-email-pekon@ti.com> (raw)
*changes from v2 (rebased)*
- rebased on [PATCH v11] mtd:nand:omap2: clean-up of supported ECC schemes
http://lists.infradead.org/pipermail/linux-mtd/2013-October/049410.html
*changes from v1 (minor)*
- rebased for newer version of previous patch-set
[PATCH v7 0/6] mtd:nand:omap2: clean-up of supported ECC schemes
http://lists.infradead.org/pipermail/linux-mtd/2013-October/048983.html
- code cleanup and formating updates
*original v1*
This patch series builds the base for adding support for newer H/W based ECC
schemes for NAND flash. This patch series
- cleans-up redundant code among various
- optimizes ecc calculation and correction paths
- improves scalability and readability, for adding newer ecc-schemes in future.
This patch affects following data-paths:
[PATCH 1/4] nand_chip->ecc.correct(): Detects and corrects ECC errors on read accesses.
[PATCH 2/4] nand_chip->ecc.calculate(): Calculates and fetches ECC syndrome from controller.
[PATCH 3/4] nand_chip->ecc.hwctl(): Configures H/W controller for Read/Write data acccesses.
[PATCH 4/4] ELM driver: add checks and updates code for scalability.
Pekon Gupta (4):
mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC schemes
mtd: nand: omap: optimize chip->ecc.calculate() for H/W ECC schemes
mtd: nand: omap: optimize chip->ecc.hwctl() for H/W ECC schemes
mtd: devices: elm: add checks ELM H/W constrains, driver code cleanup
drivers/mtd/devices/elm.c | 122 ++++---
drivers/mtd/nand/omap2.c | 704 +++++++++++++-------------------------
include/linux/platform_data/elm.h | 6 +-
3 files changed, 316 insertions(+), 516 deletions(-)
--
1.8.1
next reply other threads:[~2013-11-02 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 9:46 Pekon Gupta [this message]
2013-11-02 9:46 ` [PATCH v3 1/4] mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC schemes Pekon Gupta
2013-11-13 21:11 ` Brian Norris
2013-11-14 5:13 ` Gupta, Pekon
2013-11-02 9:46 ` [PATCH v3 2/4] mtd: nand: omap: optimize chip->ecc.calculate() " Pekon Gupta
2013-11-13 21:45 ` Brian Norris
2013-11-02 9:46 ` [PATCH v3 3/4] mtd: nand: omap: optimize chip->ecc.hwctl() " Pekon Gupta
2013-11-13 22:03 ` Brian Norris
2013-11-14 19:01 ` Ezequiel Garcia
2013-11-02 9:46 ` [PATCH v3 4/4] mtd: devices: elm: add checks ELM H/W constrains, driver code cleanup Pekon Gupta
2013-11-13 22:37 ` Brian Norris
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=1383385576-26095-1-git-send-email-pekon@ti.com \
--to=pekon@ti.com \
--cc=balbi@ti.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--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