linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Hecht <hechtb@googlemail.com>
To: linux-mtd@lists.infradead.org
Cc: Bastian Hecht <hechtb@gmail.com>,
	magnus.damm@gmail.com, laurent.pinchart@ideasonboard.com,
	linux-sh@vger.kernel.org
Subject: [PATCH v4 0/8] sh_flctl hardware ECC mode cleanup
Date: Mon, 14 May 2012 12:14:39 +0000	[thread overview]
Message-ID: <1336997687-6868-1-git-send-email-hechtb@gmail.com> (raw)

changelog v4:

  - removed arch/arm related patches
  - rebased on current l2-mtd.git
  - fixed some compiler warnings
	- patch 2: use "int irq" when removing irq binding in error case to fix smatch breakage
	- patch 7 and 8: just directly use the void __iomem pointer instead of the unprecise void pointer to fix sparse breakage

changelog v3:

Just a rebase on current l2-mtd.git.

changelog v2:
  - extract the iounmap calls from patch "Add support for error IRQ" into a new patch.
  - swapped patches "Add support for error IRQ" and "Add error IRQ resource"
  - corrected an indentation mistake

This series cleans up the flctl when run in hardware ecc mode. The first 2 patches make sure we catch all errors that result from hardware transmission. The other patches handle how the ecc is layed out, correct some code to write and read it and make sure we propagate the statistics about errors/repairs to the nand base.

Bastian Hecht (8):
  mtd: sh_flctl: Add missing iounmap()
  mtd: sh_flctl: Add support for error IRQ
  mtd: sh_flctl: Use different OOB layout
  mtd: sh_flctl: Fix hardware ECC behaviour
  mtd: sh_flctl: Simplify the hardware ecc page read/write
  mtd: sh_flctl: Group sector accesses into a single transfer
  mtd: sh_flctl: Restructure the hardware ECC handling
  mtd: sh_flctl: Use user oob data in hardware ECC mode

 drivers/mtd/nand/sh_flctl.c  |  299 ++++++++++++++++++++++++------------------
 include/linux/mtd/sh_flctl.h |   23 +++-
 2 files changed, 187 insertions(+), 135 deletions(-)

-- 
1.7.5.4


             reply	other threads:[~2012-05-14 12:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 12:14 Bastian Hecht [this message]
2012-05-14 12:14 ` [PATCH v4 1/8] mtd: sh_flctl: Add missing iounmap() Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 2/8] mtd: sh_flctl: Add support for error IRQ Bastian Hecht
2012-07-06 15:51   ` David Woodhouse
2012-07-06 16:39     ` Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 3/8] mtd: sh_flctl: Use different OOB layout Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 4/8] mtd: sh_flctl: Fix hardware ECC behaviour Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 5/8] mtd: sh_flctl: Simplify the hardware ecc page read/write Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 6/8] mtd: sh_flctl: Group sector accesses into a single transfer Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 7/8] mtd: sh_flctl: Restructure the hardware ECC handling Bastian Hecht
2012-05-14 12:14 ` [PATCH v4 8/8] mtd: sh_flctl: Use user oob data in hardware ECC mode Bastian Hecht
2012-05-14 15:12   ` Brian Norris
2012-05-16  9:37     ` Bastian Hecht
2012-05-15 10:47 ` [PATCH v4 0/8] sh_flctl hardware ECC mode cleanup Artem Bityutskiy

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=1336997687-6868-1-git-send-email-hechtb@gmail.com \
    --to=hechtb@googlemail.com \
    --cc=hechtb@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).