On Fri, Mar 9, 2018 at 4:12 PM, Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx> wrote: > This patchset adds support for SD/MMC on JZ4780 based > platforms, such as the MIPS Creator CI20 board. > > Most of the work has been done by Alex, Paul and Zubair, > while I've only prepared the upstream submission, cleaned > some patches, and written some commit logs where needed. > > All praises should go to them, all rants to me. > > The series is based on v4.16-rc4. > > Alex Smith (3): > mmc: jz4740: Set clock rate to mmc->f_max rather than JZ_MMC_CLK_RATE > mmc: jz4740: Add support for the JZ4780 > mmc: jz4740: Fix race condition in IRQ mask update > > Ezequiel Garcia (9): > mmc: jz4780: Order headers alphabetically > mmc: jz4740: Use dev_get_platdata > mmc: jz4740: Introduce devicetree probe > mmc: dt-bindings: add MMC support to JZ4740 SoC > mmc: jz4740: Use dma_request_chan() > MIPS: dts: jz4780: Add DMA controller node to the devicetree > MIPS: dts: jz4780: Add MMC controller node to the devicetree > MIPS: dts: ci20: Enable DMA and MMC in the devicetree > MIPS: configs: ci20: Enable DMA and MMC support > > Paul Cercueil (1): > mmc: jz4740: Fix error exit path in driver's probe > > Zubair Lutfullah Kakakhel (1): > mmc: jz4740: Reset the device requesting the interrupt Nice work. Entire series works just fine on my MIPS Creator CI20 (v1). Nitpick: could you update the email addresses: s/imgtec/mips/ thanks > Documentation/devicetree/bindings/mmc/jz4740.txt | 38 ++++ > arch/mips/boot/dts/ingenic/ci20.dts | 38 ++++ > arch/mips/boot/dts/ingenic/jz4780.dtsi | 54 ++++++ > arch/mips/configs/ci20_defconfig | 3 + > drivers/mmc/host/Kconfig | 2 +- > drivers/mmc/host/jz4740_mmc.c | 232 ++++++++++++++++------- > include/dt-bindings/dma/jz4780-dma.h | 49 +++++ > 7 files changed, 349 insertions(+), 67 deletions(-) > create mode 100644 Documentation/devicetree/bindings/mmc/jz4740.txt > create mode 100644 include/dt-bindings/dma/jz4780-dma.h > > -- > 2.16.2 > > -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
