arm64: dts: qcom: sm8350: Add the inline crypto engine

SM8350 has an inline crypto engine (ICE v3.2.0) next to its UFS host, but sm8350.dtsi does not describe it, so ufs-qcom runs without inline encryption. Add the compatible to the binding and the node to sm8350.dtsi, as on SM8450.

The region covers the engine (0x1d88000, 0x8000) and its key manager (0x1d90000, 0x9000), as in Qualcomm's SM8350 device tree; the clocks and the power domain are those of SM8450. The TrustZone offers the raw-key SCM calls but not GENERATE/PREPARE/IMPORT_ICE_KEY, so qcom-ice uses raw keys.

Tested on a Razer Edge 5G with fscrypt v2 on ext4: "AES-256-XTS using blk-crypto (native)", and files written with and without inlinecrypt read back correctly either way. dtbs_check is clean for all SM8350 boards.

---
Changes in v2:
- dt-bindings: drop SM8350 from the legacy single-clock list. It was
added there by mistake; SM8350 does not need the exemption, its node
has both clocks and the power domain.
- Link to v1: https://patch.msgid.link/[email protected]

---
Demeter Barna (2):
dt-bindings: crypto: qcom,inline-crypto-engine: Add SM8350
arm64: dts: qcom: sm8350: Add the inline crypto engine

 .../bindings/crypto/qcom,inline-crypto-engine.yaml          |  1 +
 arch/arm64/boot/dts/qcom/sm8350.dtsi                        | 13 +++++++++++++
 2 files changed, 14 insertions(+)

---
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
change-id: 20261105-b4-sm8350-ice-efad45e93262

Best regards,

Demeter Barna <[email protected]>

SM8350's UFS host has an inline crypto engine, version 3.2.0, with a hardware key manager behind it, clocked by the UFS ICE core and AHB clocks and powered by the UFS PHY GDSC. Document the compatible. Being a new SoC, it stays off the legacy single-clock list, so both clocks and the power domain are required.

---
 Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml | 1 +
 1 file changed, 1 insertion(+)

index 23bf98c2b..2423fd846 100644
@@ -24,6 +24,7 @@ properties:
           - qcom,sc7180-inline-crypto-engine
           - qcom,sc7280-inline-crypto-engine
           - qcom,shikra-inline-crypto-engine
+          - qcom,sm8350-inline-crypto-engine
           - qcom,sm8450-inline-crypto-engine
           - qcom,sm8550-inline-crypto-engine
           - qcom,sm8650-inline-crypto-engine

2.53.0

Best regards,
Krzysztof

Describe the UFS inline crypto engine at 0x1d88000 and hand it to the UFS host controller with qcom,ice. The region covers the engine and its hardware key manager (0x8000 + 0x9000), as in Qualcomm's SM8350 device tree; it is clocked by the UFS ICE core and AHB clocks and powered by the UFS PHY GDSC, as on SM8450. Without it the UFS driver logs "Disabling inline encryption support" and fscrypt has no hardware path.

---
 arch/arm64/boot/dts/qcom/sm8350.dtsi | 13 +++++++++++++
 1 file changed, 13 insertions(+)

index 55b32050c..2b258c4b4 100644
@@ -1782,6 +1782,8 @@ &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
 				<0 0>,
 				<0 0>,
 				<0 0>;
+			qcom,ice = <&ice>;
+
 			status = "disabled";
 		};
 

@@ -1807,6 +1809,17 @@ ufs_mem_phy: phy@1d87000 {
 			status = "disabled";
 		};
 
+		ice: crypto@1d88000 {
+			compatible = "qcom,sm8350-inline-crypto-engine",
+				     "qcom,inline-crypto-engine";
+			reg = <0 0x01d88000 0 0x11000>;
+			clocks = <&gcc GCC_UFS_PHY_ICE_CORE_CLK>,
+				 <&gcc GCC_UFS_PHY_AHB_CLK>;
+			clock-names = "core",
+				      "iface";
+			power-domains = <&gcc UFS_PHY_GDSC>;
+		};
+
 		cryptobam: dma-controller@1dc4000 {
 			compatible = "qcom,bam-v1.7.4", "qcom,bam-v1.7.0";
 			reg = <0 0x01dc4000 0 0x24000>;

2.53.0