On Tue, Nov 4, 2014 at 8:46 PM, Zhou Wang <wangzhou.bry@xxxxxxxxx> wrote: > This patchset adds the support for NAND controller of hisilicon hip04 Soc. > The NAND controller IP was developed by hisilicon and needs a new driver to > support it. This patchset is based on v3.18-rc1. I have tested that NAND flash > controller works fine in Hip04 D01 board. > > Changes in v4: > - add mtd->dev.parent = &pdev->dev, thanks Frans Klaver. > Changes in v3: > - Modify code to eliminate some code style warnings. > - add ecc-bits input check. > - avoid using waterfall style in hisi_nfc_cmdfunc(). > Changes in v2: > - Remove the patch for device tree, now patchset only has the driver and its > device tree binding documentation. > - Change the file name: hisi_nand.c to hisi504_nand.c. > Changes in v1: > - Remove callback functions out of struct hinfc_host, and call them directly > in relative functions. > - Change hinfc_read and hinfc_write from macros to inline functions. > - Instead of putting pointers, embed struct nand_chip and struct mtd_info in > struct hinfc_host directly. > - rewrite some unclear lines in device tree binding document, correct some > code style error. > > Link on v3: > - https://lkml.org/lkml/2014/10/28/386 > Link on v2: > - https://www.mail-archive.com/linux-kernel@xxxxxxxxxxxxxxx/msg750071.html > Link on v1: > - https://lkml.org/lkml/2014/7/15/198 > > Zhou Wang (2): > mtd: hisilicon: add a new NAND controller driver for hisilicon hip04 Soc > mtd: hisilicon: add device tree binding documentation > > .../devicetree/bindings/mtd/hisi504-nand.txt | 40 + > drivers/mtd/nand/Kconfig | 5 + > drivers/mtd/nand/Makefile | 1 + > drivers/mtd/nand/hisi504_nand.c | 846 ++++++++++++++++++++ > 4 files changed, 892 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mtd/hisi504-nand.txt > create mode 100644 drivers/mtd/nand/hisi504_nand.c > > -- > 1.7.9.5 > Acked-by: Haojian Zhuang <haojian.zhuang@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
