From: Boris BREZILLON <b.brezillon.dev@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Boris BREZILLON <b.brezillon.dev@gmail.com>
Subject: [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling
Date: Mon, 24 Feb 2014 18:29:51 +0100 [thread overview]
Message-ID: <1393262993-22040-1-git-send-email-b.brezillon.dev@gmail.com> (raw)
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
next reply other threads:[~2014-02-24 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:29 Boris BREZILLON [this message]
2014-02-24 17:29 ` [RFC PATCH 1/2] mtd: nand: add manufacturer specific init infrastructure Boris BREZILLON
2014-02-24 17:29 ` [RFC PATCH 2/2] mtd: nand: add hynix specific initializer Boris BREZILLON
2016-05-02 20:04 ` [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling Richard Weinberger
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=1393262993-22040-1-git-send-email-b.brezillon.dev@gmail.com \
--to=b.brezillon.dev@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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