[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1393262993-22040-1-git-send-email-b.brezillon.dev@gmail.com>
Date: Mon, 24 Feb 2014 18:29:51 +0100
From: Boris BREZILLON <b.brezillon.dev@...il.com>
To: David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
Boris BREZILLON <b.brezillon.dev@...il.com>
Subject: [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling
Hello,
This is a proposal to add support for manufacturer specific handling of
NAND chips.
Currently the only ones allowed to modify how NAND chips are accessed are
NAND controllers (by modifying the nand_chip callbacks) and NAND core code
(by setting default callbacks when these are not specified by the NAND
controller).
This series adds support for manufacturer/vendor specific handling, which is
particularly useful for read retry implementation that are (at least for
the moment) manufacturer specific.
I know there was a debate on how we should support all these READ RETRY
implementations (see http://permalink.gmane.org/gmane.linux.drivers.mtd/50603),
so please tell if I'm wrong.
Best Regards,
Boris
Boris BREZILLON (2):
mtd: nand: add manufacturer specific init infrastructure
mtd: nand: add hynix specific initializer
drivers/mtd/nand/Makefile | 2 +-
drivers/mtd/nand/nand_base.c | 7 ++
drivers/mtd/nand/nand_hynix.c | 151 +++++++++++++++++++++++++++++++++++++++++
drivers/mtd/nand/nand_ids.c | 3 +-
include/linux/mtd/nand.h | 6 ++
5 files changed, 167 insertions(+), 2 deletions(-)
create mode 100644 drivers/mtd/nand/nand_hynix.c
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists