From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, liwei213@huawei.com,
robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, guodong.xu@linaro.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
amit.kucheria@linaro.org, john.stultz@linaro.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] arm64: dts: hisilicon: hi3670: Add UFS controller support
Date: Sat, 5 Jan 2019 12:58:58 +0530 [thread overview]
Message-ID: <20190105072859.9134-3-manivannan.sadhasivam@linaro.org> (raw)
In-Reply-To: <20190105072859.9134-1-manivannan.sadhasivam@linaro.org>
Add UFS controller support for HiSilicon HI3670 SoC.
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
---
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3670.dtsi b/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
index 6ccdf5040ffd..285219dd657f 100644
--- a/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
+++ b/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
@@ -654,6 +654,24 @@
clock-names = "apb_pclk";
};
+ /* UFS */
+ ufs: ufs@ff3c0000 {
+ compatible = "hisilicon,hi3670-ufs", "jedec,ufs-2.1";
+ /* 0: HCI standard */
+ /* 1: UFS SYS CTRL */
+ reg = <0x0 0xff3c0000 0x0 0x1000>,
+ <0x0 0xff3e0000 0x0 0x1000>;
+ interrupt-parent = <&gic>;
+ interrupts = <GIC_SPI 278 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&crg_ctrl HI3670_CLK_GATE_UFSIO_REF>,
+ <&crg_ctrl HI3670_CLK_GATE_UFS_SUBSYS>;
+ clock-names = "ref_clk", "phy_clk";
+ freq-table-hz = <0 0>, <0 0>;
+ /* offset: 0x84; bit: 12 */
+ resets = <&crg_rst 0x84 12>;
+ reset-names = "rst";
+ };
+
/* SD */
dwmmc1: dwmmc1@ff37f000 {
compatible = "hisilicon,hi3670-dw-mshc";
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-05 7:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 7:28 [PATCH v2 0/3] Add UFS controller support for HI3670 SoC Manivannan Sadhasivam
2019-01-05 7:28 ` [PATCH v2 1/3] dt-bindings: ufs: Add HI3670 UFS controller binding Manivannan Sadhasivam
2019-01-11 21:35 ` Rob Herring
2019-02-16 4:08 ` Manivannan Sadhasivam
2019-02-14 6:37 ` 答复: " liwei (CM)
2019-01-05 7:28 ` Manivannan Sadhasivam [this message]
2019-02-14 6:37 ` 答复: [PATCH v2 2/3] arm64: dts: hisilicon: hi3670: Add UFS controller support liwei (CM)
2019-02-20 11:35 ` Thierry Reding
2019-02-20 14:21 ` Martin K. Petersen
2019-04-15 16:00 ` Wei Xu
2019-01-05 7:28 ` [PATCH v2 3/3] scsi: ufs: Add HI3670 SoC UFS driver support Manivannan Sadhasivam
2019-01-26 14:47 ` Manivannan Sadhasivam
2019-02-14 2:48 ` Martin K. Petersen
2019-02-16 2:59 ` Martin K. Petersen
2019-02-14 6:37 ` 答复: " liwei (CM)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190105072859.9134-3-manivannan.sadhasivam@linaro.org \
--to=manivannan.sadhasivam@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=guodong.xu@linaro.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liwei213@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=robh+dt@kernel.org \
--cc=vinholikatti@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).