Skip to content

RFC mtd: nand: add manafacturer specific handling

Boris BREZILLON linux-mtd lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2mtd: nand: add manufacturer specific init infrastructuredrivers/mtd/nand/nand_base.c include/linux/mtd/nand.h+11 -00 replies
2/2mtd: nand: add hynix specific initializerdrivers/mtd/nand/Makefile drivers/mtd/nand/nand_hynix.c drivers/mtd/nand/nand_ids.c +1 more+156 -20 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [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
Signature · 1 line
1.7.9.5