From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Qingqing Zhou <quic_qqzhou@quicinc.com>,
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 4/4] arm64: dts: qcom: qcs615: add the APPS SMMU node
Date: Thu, 17 Oct 2024 22:05:36 +0200 [thread overview]
Message-ID: <ac5081ce-e2e4-4201-bd7c-eb4ec2cf7e2d@oss.qualcomm.com> (raw)
In-Reply-To: <20241015081603.30643-5-quic_qqzhou@quicinc.com>
On 15.10.2024 10:16 AM, Qingqing Zhou wrote:
> Add the APPS SMMU node for QCS615 platform. Add the dma-ranges
> to limit DMA address range to 36bit width to align with system
> architecture.
>
> Signed-off-by: Qingqing Zhou <quic_qqzhou@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/qcs615.dtsi | 74 ++++++++++++++++++++++++++++
> 1 file changed, 74 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/qcs615.dtsi b/arch/arm64/boot/dts/qcom/qcs615.dtsi
> index 027c5125f36b..fcba83fca7cf 100644
> --- a/arch/arm64/boot/dts/qcom/qcs615.dtsi
> +++ b/arch/arm64/boot/dts/qcom/qcs615.dtsi
> @@ -379,6 +379,7 @@
> soc: soc@0 {
> compatible = "simple-bus";
> ranges = <0 0 0 0 0x10 0>;
> + dma-ranges = <0 0 0 0 0x10 0>;
> #address-cells = <2>;
> #size-cells = <2>;
>
> @@ -524,6 +525,79 @@
> reg = <0x0 0x0c3f0000 0x0 0x400>;
> };
>
> + apps_smmu: iommu@15000000 {
> + compatible = "qcom,qcs615-smmu-500", "qcom,smmu-500", "arm,mmu-500";
> + reg = <0x0 0x15000000 0x0 0x80000>;
> + #iommu-cells = <2>;
> + #global-interrupts = <1>;
> +
> + interrupts = <GIC_SPI 65 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>,
The list seems perfectly sorted, which is suspicious.. if we set
i = n - #global-interrupts, interrupt[i] signifies an error in the i-th
context bank. If the order is wrong, we'll get bogus reports
Also, this is not aligned properly ('<' under '<')
Konrad
next prev parent reply other threads:[~2024-10-17 20:05 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 [this message]
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
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=ac5081ce-e2e4-4201-bd7c-eb4ec2cf7e2d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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=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;
as well as URLs for NNTP newsgroup(s).