From: Qingqing Zhou <quic_qqzhou@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <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>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <iommu@lists.linux.dev>
Subject: Re: [PATCH v2 0/4] Add support for APPS SMMU on QCS615
Date: Tue, 15 Oct 2024 17:53:52 +0800 [thread overview]
Message-ID: <85a13e7c-b48c-4105-a633-a48ebebe9fdf@quicinc.com> (raw)
In-Reply-To: <e0bd108f-1133-473a-a0e5-6efe1b19f50d@kernel.org>
在 10/15/2024 4:20 PM, Krzysztof Kozlowski 写道:
> On 15/10/2024 10:15, Qingqing Zhou wrote:
>> Enable APPS SMMU function on QCS615 platform. APPS SMMU is required
>> for address translation in devices including Ethernet/UFS/USB and
>> so on.
>>
>> Add the SCM node for SMMU probing normally. SMMU driver probe will
>> check qcom_scm ready or not, without SCM node, SMMU driver probe will
>> defer.
>> The dmesg log without SCM node:
>> platform 15000000.iommu: deferred probe pending: arm-smmu: qcom_scm not ready
>>
>> With the SCM node, SMMU can probe normally, but SCM driver still fails
>> to probe because of one SCM bug:
>> qcom_scm firmware:scm: error (____ptrval____): Failed to enable the TrustZone memory allocator
>> qcom_scm firmware:scm: probe with driver qcom_scm failed with error 4
>> The above SCM bug is fixed by:
>> https://lore.kernel.org/all/20241005140150.4109700-2-quic_kuldsing@quicinc.com/
>> But above patch doesn't impact building of current patch series, this patch
>> series can build successfully without above patch.
>>
>> Dependency:
>> https://lore.kernel.org/all/20240926-add_initial_support_for_qcs615-v3-0-e37617e91c62@quicinc.com/
>>
>> Changes in v2:
>> - Address the comments on bindings from Krzysztof.
>
> Which comments? Be specific what changed.
Got it, will change into "Add QCS615 into compatibles disallowing clocks in arm,smmu.yaml to address the comments in arm,smmu bindings patch from Krzysztof." in next version. Is it fine?
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2024-10-15 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 8:15 [PATCH v2 0/4] Add support for APPS SMMU on QCS615 Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 1/4] dt-bindings: firmware: qcom,scm: document QCS615 SCM Qingqing Zhou
2024-10-15 8:21 ` Krzysztof Kozlowski
2024-10-15 8:50 ` Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 2/4] dt-bindings: arm-smmu: document QCS615 APPS SMMU Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 3/4] arm64: dts: qcom: qcs615: add the SCM node Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 4/4] arm64: dts: qcom: qcs615: add the APPS SMMU node Qingqing Zhou
2024-10-17 20:05 ` Konrad Dybcio
2024-10-18 6:20 ` Qingqing Zhou
2024-10-23 5:48 ` Qingqing Zhou
2024-10-25 17:26 ` Konrad Dybcio
2024-10-15 8:20 ` [PATCH v2 0/4] Add support for APPS SMMU on QCS615 Krzysztof Kozlowski
2024-10-15 9:53 ` Qingqing Zhou [this message]
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=85a13e7c-b48c-4105-a633-a48ebebe9fdf@quicinc.com \
--to=quic_qqzhou@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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;
as well as URLs for NNTP newsgroup(s).