1QCOM Secure Channel Manager (SCM) 2 3Qualcomm processors include an interface to communicate to the secure firmware. 4This interface allows for clients to request different types of actions. These 5can include CPU power up/down, HDCP requests, loading of firmware, and other 6assorted actions. 7 8Required properties: 9- compatible: must contain one of the following: 10 * "qcom,scm-apq8064" 11 * "qcom,scm-apq8084" 12 * "qcom,scm-ipq4019" 13 * "qcom,scm-ipq806x" 14 * "qcom,scm-ipq8074" 15 * "qcom,scm-mdm9607" 16 * "qcom,scm-msm8660" 17 * "qcom,scm-msm8916" 18 * "qcom,scm-msm8960" 19 * "qcom,scm-msm8974" 20 * "qcom,scm-msm8994" 21 * "qcom,scm-msm8996" 22 * "qcom,scm-msm8998" 23 * "qcom,scm-sc7180" 24 * "qcom,scm-sc7280" 25 * "qcom,scm-sdm845" 26 * "qcom,scm-sdx55" 27 * "qcom,scm-sm8150" 28 * "qcom,scm-sm8250" 29 * "qcom,scm-sm8350" 30 and: 31 * "qcom,scm" 32- clocks: Specifies clocks needed by the SCM interface, if any: 33 * core clock required for "qcom,scm-apq8064", "qcom,scm-msm8660" and 34 "qcom,scm-msm8960" 35 * core, iface and bus clocks required for "qcom,scm-apq8084", 36 "qcom,scm-msm8916" and "qcom,scm-msm8974" 37- clock-names: Must contain "core" for the core clock, "iface" for the interface 38 clock and "bus" for the bus clock per the requirements of the compatible. 39- qcom,dload-mode: phandle to the TCSR hardware block and offset of the 40 download mode control register (optional) 41 42Example for MSM8916: 43 44 firmware { 45 scm { 46 compatible = "qcom,msm8916", "qcom,scm"; 47 clocks = <&gcc GCC_CRYPTO_CLK> , 48 <&gcc GCC_CRYPTO_AXI_CLK>, 49 <&gcc GCC_CRYPTO_AHB_CLK>; 50 clock-names = "core", "bus", "iface"; 51 }; 52 }; 53