From: Bjorn Andersson <andersson@kernel.org>
To: 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,
Qingqing Zhou <quic_qqzhou@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: (subset) [PATCH v4 0/3] Add support for APPS SMMU on QCS615
Date: Mon, 2 Dec 2024 09:51:04 -0600 [thread overview]
Message-ID: <173315466530.263019.10143861935675163068.b4-ty@kernel.org> (raw)
In-Reply-To: <20241105032107.9552-1-quic_qqzhou@quicinc.com>
On Tue, 05 Nov 2024 08:51:04 +0530, 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
>
> [...]
Applied, thanks!
[2/3] arm64: dts: qcom: qcs615: add the SCM node
commit: 8c7f9d73de1bdb72d114aab053c8f7e3e9b32176
[3/3] arm64: dts: qcom: qcs615: add the APPS SMMU node
commit: 58241be90050e53b7148a43dafa94c999867cbb7
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-12-02 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 3:21 Qingqing Zhou
2024-11-05 3:21 ` [PATCH v4 1/3] dt-bindings: firmware: qcom,scm: document QCS615 SCM Qingqing Zhou
2024-11-05 3:21 ` [PATCH v4 2/3] arm64: dts: qcom: qcs615: add the SCM node Qingqing Zhou
2024-11-05 3:21 ` [PATCH v4 3/3] arm64: dts: qcom: qcs615: add the APPS SMMU node Qingqing Zhou
2024-11-18 10:04 ` Qingqing Zhou
2024-11-18 13:22 ` Dmitry Baryshkov
2024-12-02 14:30 ` Konrad Dybcio
2024-12-02 15:51 ` Bjorn Andersson [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=173315466530.263019.10143861935675163068.b4-ty@kernel.org \
--to=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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_qqzhou@quicinc.com \
--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
all inboxes | Powered by JetHome®