Message ID | 20180213101412.5717-1-liwei213@huawei.com |
---|---|
Headers | show |
Series | scsi: ufs: add ufs driver code for Hisilicon Hi3660 SoC | expand |
Li, > 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 Is the intent for this series to go through the SCSI tree? If so, I'll need some acks from the ARM maintainers for the dt/platform changes.
Hi Li Wei, On 2018/2/13 10:14, Li Wei wrote: > arm64: dts: add ufs node for Hisilicon. > > Signed-off-by: Li Wei <liwei213@huawei.com> Fine to me. Thanks! Acked-by: Wei Xu <xuwei5@hisilicon.com> Best Regards, Wei > --- > arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 19 +++++++++++++++++++ > 1 file changed, 19 insertions(+) > > diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi > index ab0b95ba5ae5..d0dfa97fdad1 100644 > --- a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi > +++ b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi > @@ -904,6 +904,25 @@ > reset-gpios = <&gpio11 1 0 >; > }; > > + /* UFS */ > + ufs: ufs@ff3b0000 { > + compatible = "hisilicon,hi3660-ufs", "jedec,ufs-1.1"; > + /* 0: HCI standard */ > + /* 1: UFS SYS CTRL */ > + reg = <0x0 0xff3b0000 0x0 0x1000>, > + <0x0 0xff3b1000 0x0 0x1000>; > + interrupt-parent = <&gic>; > + interrupts = <GIC_SPI 278 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&crg_ctrl HI3660_CLK_GATE_UFSIO_REF>, > + <&crg_ctrl HI3660_CLK_GATE_UFSPHY_CFG>; > + clock-names = "ref_clk", "phy_clk"; > + /* offset: 0x84; bit: 12 */ > + /* offset: 0x84; bit: 7 */ > + resets = <&crg_rst 0x84 12>, > + <&crg_rst 0x84 7>; > + reset-names = "rst", "assert"; > + }; > + > /* SD */ > dwmmc1: dwmmc1@ff37f000 { > #address-cells = <1>; > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html