From: Qingqing Zhou <quic_qqzhou@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <andersson@kernel.org>, <konradybcio@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<robimarko@gmail.com>, <will@kernel.org>, <robin.murphy@arm.com>,
<joro@8bytes.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<iommu@lists.linux.dev>
Subject: Re: [PATCH v3 3/4] arm64: dts: qcom: qcs615: add the SCM node
Date: Wed, 30 Oct 2024 16:42:19 +0800 [thread overview]
Message-ID: <645c9887-4df2-4ab2-a048-ba79a97b8d2f@quicinc.com> (raw)
In-Reply-To: <flk7n534gfqyivlbl72qco4k5d3c6ravevumjfoh6464pe3qg4@r7ns6zr2i3bv>
在 10/25/2024 2:02 PM, Dmitry Baryshkov 写道:
> On Fri, Oct 25, 2024 at 08:37:31AM +0530, Qingqing Zhou wrote:
>> Add the SCM node for QCS615 platform. It is an interface to
>> communicate to the secure firmware.
>>
>> Signed-off-by: Qingqing Zhou <quic_qqzhou@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs615.dtsi | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs615.dtsi b/arch/arm64/boot/dts/qcom/qcs615.dtsi
>> index ac4c4c751da1..027c5125f36b 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs615.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/qcs615.dtsi
>> @@ -278,6 +278,13 @@
>> reg = <0 0x80000000 0 0>;
>> };
>>
>> + firmware {
>> + scm {
>> + compatible = "qcom,scm-qcs615", "qcom,scm";
>> + qcom,dload-mode = <&tcsr 0x13000>;
>
> No CRYPTO clock?
NO, response from Qualcomm clock team is "the current QCS615 RPMH code does not have the clock support for CE clock", so we don't configure clocks here.
>
>> + };
>> + };
>> +
>> camnoc_virt: interconnect-0 {
>> compatible = "qcom,qcs615-camnoc-virt";
>> #interconnect-cells = <2>;
>> --
>> 2.17.1
>>
>
next prev parent reply other threads:[~2024-10-30 8:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 3:07 [PATCH v3 0/4] Add support for APPS SMMU on QCS615 Qingqing Zhou
2024-10-25 3:07 ` [PATCH v3 1/4] dt-bindings: firmware: qcom,scm: document QCS615 SCM Qingqing Zhou
2024-10-25 3:07 ` [PATCH v3 2/4] dt-bindings: arm-smmu: document QCS615 APPS SMMU Qingqing Zhou
2024-10-25 12:34 ` Krzysztof Kozlowski
2024-10-25 3:07 ` [PATCH v3 3/4] arm64: dts: qcom: qcs615: add the SCM node Qingqing Zhou
2024-10-25 6:02 ` Dmitry Baryshkov
2024-10-30 8:42 ` Qingqing Zhou [this message]
2024-10-31 18:59 ` Dmitry Baryshkov
2024-11-04 7:36 ` Qingqing Zhou
2024-11-04 10:54 ` Dmitry Baryshkov
2024-10-25 3:07 ` [PATCH v3 4/4] arm64: dts: qcom: qcs615: add the APPS SMMU node Qingqing Zhou
2024-10-25 8:54 ` Konrad Dybcio
2024-10-25 11:06 ` Dmitry Baryshkov
2024-10-25 16:45 ` Konrad Dybcio
2024-10-26 18:18 ` Dmitry Baryshkov
2024-10-28 15:46 ` Konrad Dybcio
2024-10-30 8:21 ` Qingqing Zhou
2024-10-29 16:15 ` [PATCH v3 0/4] Add support for APPS SMMU on QCS615 Will Deacon
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=645c9887-4df2-4ab2-a048-ba79a97b8d2f@quicinc.com \
--to=quic_qqzhou@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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