linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-scsi@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-fscrypt@vger.kernel.org,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Andy Gross <agross@kernel.org>, Avri Altman <avri.altman@wdc.com>,
	Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Can Guo <cang@codeaurora.org>,
	Elliot Berman <eberman@codeaurora.org>,
	John Stultz <john.stultz@linaro.org>,
	Satya Tangirala <satyat@google.com>,
	Steev Klimaszewski <steev@kali.org>,
	Thara Gopinath <thara.gopinath@linaro.org>
Subject: [PATCH v6 3/5] arm64: dts: sdm845: add Inline Crypto Engine registers and clock
Date: Fri, 10 Jul 2020 00:20:10 -0700	[thread overview]
Message-ID: <20200710072013.177481-4-ebiggers@kernel.org> (raw)
In-Reply-To: <20200710072013.177481-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

Add the vendor-specific registers and clock for Qualcomm ICE (Inline
Crypto Engine) to the device tree node for the UFS host controller on
sdm845, so that the ufs-qcom driver will be able to use inline crypto.

Use a separate register range rather than extending the main UFS range
because there's a gap between the two, and the ICE registers are
vendor-specific.  (Actually, the hardware claims that the ICE range also
includes the array of standard crypto configuration registers; however,
on this SoC the Linux kernel isn't permitted to access them directly.)

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 arch/arm64/boot/dts/qcom/sdm845.dtsi | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
index 8eb5a31346d2..0affb0041724 100644
--- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
@@ -1692,7 +1692,9 @@ mmss_noc: interconnect@1740000 {
 		ufs_mem_hc: ufshc@1d84000 {
 			compatible = "qcom,sdm845-ufshc", "qcom,ufshc",
 				     "jedec,ufs-2.0";
-			reg = <0 0x01d84000 0 0x2500>;
+			reg = <0 0x01d84000 0 0x2500>,
+			      <0 0x01d90000 0 0x8000>;
+			reg-names = "std", "ice";
 			interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>;
 			phys = <&ufs_mem_phy_lanes>;
 			phy-names = "ufsphy";
@@ -1712,7 +1714,8 @@ ufs_mem_hc: ufshc@1d84000 {
 				"ref_clk",
 				"tx_lane0_sync_clk",
 				"rx_lane0_sync_clk",
-				"rx_lane1_sync_clk";
+				"rx_lane1_sync_clk",
+				"ice_core_clk";
 			clocks =
 				<&gcc GCC_UFS_PHY_AXI_CLK>,
 				<&gcc GCC_AGGRE_UFS_PHY_AXI_CLK>,
@@ -1721,7 +1724,8 @@ ufs_mem_hc: ufshc@1d84000 {
 				<&rpmhcc RPMH_CXO_CLK>,
 				<&gcc GCC_UFS_PHY_TX_SYMBOL_0_CLK>,
 				<&gcc GCC_UFS_PHY_RX_SYMBOL_0_CLK>,
-				<&gcc GCC_UFS_PHY_RX_SYMBOL_1_CLK>;
+				<&gcc GCC_UFS_PHY_RX_SYMBOL_1_CLK>,
+				<&gcc GCC_UFS_PHY_ICE_CORE_CLK>;
 			freq-table-hz =
 				<50000000 200000000>,
 				<0 0>,
@@ -1730,7 +1734,8 @@ ufs_mem_hc: ufshc@1d84000 {
 				<0 0>,
 				<0 0>,
 				<0 0>,
-				<0 0>;
+				<0 0>,
+				<0 300000000>;
 
 			status = "disabled";
 		};
-- 
2.27.0


  parent reply	other threads:[~2020-07-10  7:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  7:20 [PATCH v6 0/5] Inline crypto support on DragonBoard 845c Eric Biggers
2020-07-10  7:20 ` [PATCH v6 1/5] firmware: qcom_scm: Add support for programming inline crypto keys Eric Biggers
2020-07-10  7:20 ` [PATCH v6 2/5] scsi: ufs-qcom: name the dev_ref_clk_ctrl registers Eric Biggers
2020-07-12  8:42   ` Avri Altman
2020-07-22  5:07   ` Bjorn Andersson
2020-07-10  7:20 ` Eric Biggers [this message]
2020-07-14 14:16   ` [PATCH v6 3/5] arm64: dts: sdm845: add Inline Crypto Engine registers and clock Martin K. Petersen
2020-07-14 16:15     ` Eric Biggers
2020-07-14 16:35       ` Rob Herring
2020-07-14 16:43         ` Eric Biggers
2020-07-14 16:46           ` Martin K. Petersen
2020-07-14 16:59           ` Rob Herring
2020-07-14 17:12             ` Eric Biggers
2020-07-14 17:31               ` Bjorn Andersson
2020-07-14 17:43                 ` Bjorn Andersson
2020-07-14 17:57                   ` Eric Biggers
2020-07-14 20:00                     ` Bjorn Andersson
2020-07-15  3:00                       ` Eric Biggers
2020-07-20 17:07                         ` Eric Biggers
2020-07-21 18:20                           ` Eric Biggers
2020-07-22  5:11                           ` Bjorn Andersson
2020-07-14 17:36               ` Rob Herring
2020-07-10  7:20 ` [PATCH v6 4/5] scsi: ufs: add program_key() variant op Eric Biggers
2020-07-12  9:41   ` Avri Altman
2020-07-10  7:20 ` [PATCH v6 5/5] scsi: ufs-qcom: add Inline Crypto Engine support Eric Biggers
2020-07-12  9:43   ` Avri Altman
2020-07-22  5:09   ` Bjorn Andersson
2020-07-22  4:28 ` [PATCH v6 0/5] Inline crypto support on DragonBoard 845c Martin K. Petersen
2020-07-22  5:25   ` Eric Biggers
2020-07-22 12:21     ` Martin K. Petersen

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=20200710072013.177481-4-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=agross@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=bmuthuku@qti.qualcomm.com \
    --cc=cang@codeaurora.org \
    --cc=eberman@codeaurora.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=satyat@google.com \
    --cc=steev@kali.org \
    --cc=thara.gopinath@linaro.org \
    /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).