From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v9 0/4] mtd: nand: omap: optimize OMAP NAND driver
Date: Fri, 06 Dec 2013 08:00:41 +0100 [thread overview]
Message-ID: <52A17619.7070801@denx.de> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA52408@DBDE04.ent.ti.com>
On 06.12.2013 07:22, Gupta, Pekon wrote:
>> From: Gupta, Pekon
>> Subject: [PATCH v9 0/4] mtd: nand: omap: optimize OMAP NAND driver
>>
>> OMAP NAND drivers support various ecc-schemes like (HAM1, BCH4, BCH8..)
>> And, each ecc-scheme usually has 2 implementations
>> - HAM1_HW or BCHx_HW (using in-build h/w engine for all computation)
>> - HAM1_SW or BCHx_HW_DETECTION_SW) (using software library for some computation)
>>
>> This patch series is Part-2 (split) from earlier series, as mentioned below:
>> http://lists.denx.de/pipermail/u-boot/2013-November/167270.html
>>
>> This series aims at following:
>> - cleans-up redundant code, duplicate in different ecc-schemes
>> - optimizes ecc calculation and correction paths
>> - improves scalability and readability, for adding newer ecc-schemes in future.
>> - updates following callbacks for different ecc-schmes:
>> [PATCH 1/4] nand_chip->ecc.hwctl(): configures h/w controller before for Read/Write acccess
>> [PATCH 2/4] nand_chip->ecc.calculate(): calculates and fetches ECC syndrome from h/w controller.
>> [PATCH 3/4] nand_chip->ecc.correct(): detects and corrects ECC errors on read access
>> [PATCH 4/4] update doc and README
>>
>>
>> *changes in v9*
>> - split from main series, rebased and forked independently
>>
>
> Request you to please review this series. And accept it if it looks okay.
>
> And a bug-fix which causes regression for x8 NAND devices
> using HAM1 ecc-scheme. This was reported & (un-officially)
> tested by Stefan Roese <sr@denx.de>.
I tested this patch series plus the fix from Pekon on an x8 and x16
OMAP3530 board. Both without any problems. So for this series:
Tested-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
prev parent reply other threads:[~2013-12-06 7:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 5:32 [U-Boot] [PATCH v9 0/4] mtd: nand: omap: optimize OMAP NAND driver Pekon Gupta
2013-11-19 5:32 ` [U-Boot] [PATCH v9 1/4] mtd: nand: omap: optimize chip->ecc.hwctl() for H/W ECC schemes Pekon Gupta
2013-11-19 5:32 ` [U-Boot] [PATCH v9 2/4] mtd: nand: omap: optimize chip->ecc.calculate() " Pekon Gupta
2013-11-19 5:32 ` [U-Boot] [PATCH v9 3/4] mtd: nand: omap: optimized chip->ecc.correct() " Pekon Gupta
2013-11-19 5:32 ` [U-Boot] [PATCH v9 4/4] board/ti/am335x/README: update for NAND boot Pekon Gupta
2013-11-19 11:27 ` [U-Boot] [PATCH v9 0/4] mtd: nand: omap: optimize OMAP NAND driver Abraham V.
2013-11-19 12:04 ` Gupta, Pekon
2013-11-19 12:13 ` Ezequiel Garcia
2013-12-06 6:22 ` Gupta, Pekon
2013-12-06 7:00 ` Stefan Roese [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=52A17619.7070801@denx.de \
--to=sr@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox