[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b746166-e165-23c4-fc90-a6ba77ac4d7a@linaro.org>
Date: Tue, 14 Feb 2023 13:47:52 +0100
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Abel Vesa <abel.vesa@...aro.org>, Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
"James E . J . Bottomley" <jejb@...ux.ibm.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
Manivannan Sadhasivam <mani@...nel.org>,
Eric Biggers <ebiggers@...gle.com>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-mmc@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [RFC PATCH 2/5] arm64: dts: qcom: sm8450: Add the Inline Crypto
Engine node
On 14.02.2023 13:02, Abel Vesa wrote:
> Drop all values related to the ICE from the UFS HC node and add a
> dedicated ICE node. Also enable it in HDK board dts.
>
> Signed-off-by: Abel Vesa <abel.vesa@...aro.org>
> ---
> arch/arm64/boot/dts/qcom/sm8450-hdk.dts | 4 ++++
> arch/arm64/boot/dts/qcom/sm8450.dtsi | 24 +++++++++++++++---------
> 2 files changed, 19 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8450-hdk.dts b/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> index feef3837e4cd..de631deef1e8 100644
> --- a/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> @@ -461,6 +461,10 @@ lt9611_out: endpoint {
> };
> };
>
> +&ice {
> + status = "okay";
> +};
> +
> &mdss {
> status = "okay";
> };
> diff --git a/arch/arm64/boot/dts/qcom/sm8450.dtsi b/arch/arm64/boot/dts/qcom/sm8450.dtsi
> index 1a744a33bcf4..34d569f6c239 100644
> --- a/arch/arm64/boot/dts/qcom/sm8450.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8450.dtsi
> @@ -3989,9 +3989,8 @@ system-cache-controller@...00000 {
> ufs_mem_hc: ufshc@...4000 {
> compatible = "qcom,sm8450-ufshc", "qcom,ufshc",
> "jedec,ufs-2.0";
> - reg = <0 0x01d84000 0 0x3000>,
> - <0 0x01d88000 0 0x8000>;
> - reg-names = "std", "ice";
> + reg = <0 0x01d84000 0 0x3000>;
> + reg-names = "std";
> interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>;
> phys = <&ufs_mem_phy_lanes>;
> phy-names = "ufsphy";
> @@ -4015,8 +4014,7 @@ ufs_mem_hc: ufshc@...4000 {
> "ref_clk",
> "tx_lane0_sync_clk",
> "rx_lane0_sync_clk",
> - "rx_lane1_sync_clk",
> - "ice_core_clk";
> + "rx_lane1_sync_clk";
> clocks =
> <&gcc GCC_UFS_PHY_AXI_CLK>,
> <&gcc GCC_AGGRE_UFS_PHY_AXI_CLK>,
> @@ -4025,8 +4023,7 @@ ufs_mem_hc: ufshc@...4000 {
> <&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_ICE_CORE_CLK>;
> + <&gcc GCC_UFS_PHY_RX_SYMBOL_1_CLK>;
> freq-table-hz =
> <75000000 300000000>,
> <0 0>,
> @@ -4035,8 +4032,17 @@ ufs_mem_hc: ufshc@...4000 {
> <75000000 300000000>,
> <0 0>,
> <0 0>,
> - <0 0>,
> - <75000000 300000000>;
> + <0 0>;
> + qcom,ice = <&ice>;
> +
> + status = "disabled";
> + };
> +
> + ice: inline-crypto-engine {
> + compatible = "qcom,inline-crypto-engine";
> + reg = <0 0x01d88000 0 0x8000>;
> + clocks = <&gcc GCC_UFS_PHY_ICE_CORE_CLK>;
> +
> status = "disabled";
Any reason for this guy to be disabled?
Konrad
> };
>
Powered by blists - more mailing lists