Hi, On 25/05/18 10:17, Li Wei wrote: > This patchset adds driver support for UFS for Hi3660 SoC. It is verified on HiKey960 board. > > Li Wei (5): > scsi: ufs: add Hisilicon ufs driver code > dt-bindings: scsi: ufs: add document for hisi-ufs > arm64: dts: add ufs dts node > arm64: defconfig: enable configs for Hisilicon ufs > arm64: defconfig: enable f2fs and squashfs > > Documentation/devicetree/bindings/ufs/ufs-hisi.txt | 41 ++ > .../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 10 +- > arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 18 + > arch/arm64/configs/defconfig | 11 + > drivers/scsi/ufs/Kconfig | 9 + > drivers/scsi/ufs/Makefile | 1 + > drivers/scsi/ufs/ufs-hisi.c | 619 +++++++++++++++++++++ > drivers/scsi/ufs/ufs-hisi.h | 115 ++++ > 8 files changed, 821 insertions(+), 3 deletions(-) > create mode 100644 Documentation/devicetree/bindings/ufs/ufs-hisi.txt > create mode 100644 drivers/scsi/ufs/ufs-hisi.c > create mode 100644 drivers/scsi/ufs/ufs-hisi.h > > Major changes in v10: > - solve review comments from Rob Herring. > *Modify the "reset-names" describe in ufs-hisi.txt binding file. > *List clocks in ufs-hisi.txt binding file. > *remove the "arst" and keep only "rst" in the binging files. > *remove the "arst" member from both dts and c code. > Major changes in v9: > - solve review comments from Rob Herring. > *remove freq-table-hz in ufs-hisi.txt binding file. > *Move the rst to the ufshcd_pltfm.txt common binding file. > *Modify the member "assert" of UFS host structure to "arst". > Major changes in v8: > - solve review comments from zhangfei. > *Add Version history. > - solve review comments from Rob Herring. > *remove freq-table-hz. > - solve review comments from Riku Voipio. > *Add MODULE_DEVICE_TABLE for ufs driver. > Tested on top of linux-next (4.17.0-next-20180605), I can reliably load my debian userspace flashed on the 'system' fastboot partition. Tested-by: Valentin Schneider <valentin.schneider@xxxxxxx> -- 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