v2: 1. Addressed the review comments given in v1 2. Removed the DMA coherent buffer for register read and used streaming DMA API’s 3. Reorganized the NAND read and write functions 4. Separated patch for driver and documentation changes 5. Changed the compatible string for EBI2 v1: http://www.spinics.net/lists/devicetree/msg183706.html Abhishek Sahu (25): mtd: nand: qcom: fix config error for BCH mtd: nand: qcom: program NAND_DEV_CMD_VLD register mtd: nand: qcom: change compatible string for EBI2 NANDC dt-bindings: qcom_nandc: change compatible string for EBI2 NANDC mtd: nand: qcom: remove redundant chip select compatible string dt-bindings: qcom_nandc: remove chip select compatible string mtd: nand: qcom: reorganize nand page read mtd: nand: qcom: reorganize nand page write mtd: nand: qcom: remove memset for clearing read register buffer mtd: nand: qcom: reorganize nand devices probing mtd: nand: qcom: support for NAND controller properties dt-bindings: qcom_nandc: QPIC NAND documentation mtd: nand: qcom: add QPIC NAND compatible string mtd: nand: qcom: add and initialize QPIC DMA resources mtd: nand: qcom: DMA mapping support for register read buffer mtd: nand: qcom: allocate BAM transaction mtd: nand: qcom: add BAM DMA descriptor handling mtd: nand: qcom: support for passing flags in transfer functions mtd: nand: qcom: support for read location registers mtd: nand: qcom: erased codeword detection configuration mtd: nand: qcom: support for QPIC page read/write mtd: nand: qcom: QPIC raw write support mtd: nand: qcom: change register offset defines with enums dt-bindings: qcom_nandc: compatible string for version 1.5.0 mtd: nand: qcom: support for QPIC version 1.5.0 .../devicetree/bindings/mtd/qcom_nandc.txt | 56 +- drivers/mtd/nand/qcom_nandc.c | 1157 ++++++++++++++++---- 2 files changed, 1010 insertions(+), 203 deletions(-) -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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
