From: Brian Norris <computersforpeace@gmail.com>
To: <linux-mtd@lists.infradead.org>
Cc: Florian Fainelli <ffainelli@freebox.fr>,
Jamie Iles <jamie@jamieiles.com>,
Prabhakar Kushwaha <prabhakar@freescale.com>,
Mike Dunn <mikedunn@newsguy.com>,
Kevin Cernekee <cernekee@gmail.com>,
eric miao <eric.miao@marvell.com>, Axel Lin <axel.lin@gmail.com>,
Li Yang <leoli@freescale.com>,
Bastian Hecht <hechtb@googlemail.com>,
Mike Frysinger <vapier.adi@gmail.com>,
Lei Wen <leiwen@marvell.com>,
Scott Wood <scottwood@freescale.com>,
Thomas Gleixner <tglx@linutronix.de>,
Bryan Wu <cooloney@kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Matthieu CASTET <matthieu.castet@parrot.com>,
Huang Shijie <b32955@freescale.com>,
Shmulik Ladkani <shmulik.ladkani@gmail.com>,
Jiandong Zheng <jdzheng@broadcom.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: [PATCH v4 00/10] mtd: nand: rework nand_ecc_ctrl interface for OOB
Date: Wed, 2 May 2012 10:14:54 -0700 [thread overview]
Message-ID: <1335978904-8005-1-git-send-email-computersforpeace@gmail.com> (raw)
Hello,
This is the fourth version of my patches to change the nand_chip and
nand_ecc_ctrl interfaces so that the nand_ecc_ctrl functions have information
about whether the higher layers actually need OOB data to be read/written
from/to the NAND device.
Changes for v4, somewhat ordered by importance:
Fixup unsafe behavior for Freescale NAND drivers (thanks Scott)
Rebase on auto-increment fixes (sent separately; not accepted yet). Some of
the nand_base support I provided was not sound for NAND that used
auto-increment. But we always had NAND_NO_AUTOINCR set, so I killed the
option and dropped support for auto-increment, making the nand_base changes
sound again.
Rebase on top of Mike Dunn's bitflip threshold patch. There wasn't really any
conflict; just trivial automerges.
Applied Ack's, Reviewed-by's
Please refer to previous communications for other info.
I could not compile all the affected drivers, since some required ARCH-specific
builds that I am not familiar with.
Developers: if you care about your driver, please compile test and review to be
sure I'm doing things safely for you.
Note to the maintainers: please do NOT accept any of the patches 3-10 without
an explicit ACK from someone who knows the driver (I included Ack's for 6, 7,
and 8). I think they're simple, but I am not certain. And it is totally safe to
ignore one or several of those patches independently.
Thanks for reviewing!
Brian
Brian Norris (10):
mtd: nand: add 'oob_required' argument to NAND {read,write}_page
interfaces
mtd: nand: pass proper 'oob_required' parameter
mtd: Blackfin NFC: utilize oob_required parameter
mtd: cafe_nand: utilize oob_required parameter
mtd: denali: utilize oob_required parameter
mtd: eLBC NAND: utilize oob_required parameter
mtd: IFC NAND: utilize oob_required parameter
mtd: gpmi-nand: utilize oob_requested parameter
mtd: nand: utilize oob_required parameter
mtd: pxa3xx_nand: utilize oob_required parameter
drivers/mtd/nand/atmel_nand.c | 5 +-
drivers/mtd/nand/bcm_umi_bch.c | 10 +++--
drivers/mtd/nand/bcm_umi_nand.c | 2 +-
drivers/mtd/nand/bf5xx_nand.c | 10 +++--
drivers/mtd/nand/cafe_nand.c | 16 +++++---
drivers/mtd/nand/denali.c | 12 +++--
drivers/mtd/nand/docg4.c | 12 +++---
drivers/mtd/nand/fsl_elbc_nand.c | 14 +++----
drivers/mtd/nand/fsl_ifc_nand.c | 13 +++---
drivers/mtd/nand/fsmc_nand.c | 3 +-
drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 41 ++++++++++---------
drivers/mtd/nand/nand_base.c | 70 ++++++++++++++++++++------------
drivers/mtd/nand/pxa3xx_nand.c | 11 +++--
drivers/mtd/nand/sh_flctl.c | 4 +-
include/linux/mtd/nand.h | 11 +++--
15 files changed, 134 insertions(+), 100 deletions(-)
--
1.7.5.4.2.g519b1
next reply other threads:[~2012-05-02 17:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 17:14 Brian Norris [this message]
2012-05-02 17:14 ` [PATCH v4 01/10] mtd: nand: add 'oob_required' argument to NAND {read, write}_page interfaces Brian Norris
2012-05-03 17:16 ` Mike Dunn
2012-05-03 17:43 ` Shmulik Ladkani
2012-05-03 22:34 ` Brian Norris
2012-05-04 7:58 ` Artem Bityutskiy
2012-05-02 17:14 ` [PATCH v4 02/10] mtd: nand: pass proper 'oob_required' parameter Brian Norris
2012-05-02 17:14 ` [PATCH v4 03/10] mtd: Blackfin NFC: utilize oob_required parameter Brian Norris
2012-05-03 9:55 ` Artem Bityutskiy
2012-05-02 17:14 ` [PATCH v4 04/10] mtd: cafe_nand: " Brian Norris
2012-05-02 17:14 ` [PATCH v4 05/10] mtd: denali: " Brian Norris
2012-05-02 17:15 ` [PATCH v4 06/10] mtd: eLBC NAND: " Brian Norris
2012-05-02 17:15 ` [PATCH v4 07/10] mtd: IFC " Brian Norris
2012-05-02 17:15 ` [PATCH v4 08/10] mtd: gpmi-nand: utilize oob_requested parameter Brian Norris
2012-05-02 17:15 ` [PATCH v4 09/10] mtd: nand: utilize oob_required parameter Brian Norris
2012-05-02 17:15 ` [PATCH v4 10/10] mtd: pxa3xx_nand: " Brian Norris
2012-05-03 10:00 ` [PATCH v4 00/10] mtd: nand: rework nand_ecc_ctrl interface for OOB Artem Bityutskiy
2012-05-03 17:11 ` Mike Dunn
2012-05-04 7:23 ` 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=1335978904-8005-1-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=axel.lin@gmail.com \
--cc=b32955@freescale.com \
--cc=cernekee@gmail.com \
--cc=cooloney@kernel.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.miao@marvell.com \
--cc=ffainelli@freebox.fr \
--cc=hechtb@googlemail.com \
--cc=jamie@jamieiles.com \
--cc=jdzheng@broadcom.com \
--cc=leiwen@marvell.com \
--cc=leoli@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
--cc=mikedunn@newsguy.com \
--cc=prabhakar@freescale.com \
--cc=scottwood@freescale.com \
--cc=shmulik.ladkani@gmail.com \
--cc=tglx@linutronix.de \
--cc=vapier.adi@gmail.com \
--cc=w.sang@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.