From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: 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,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH v3 4/4] arm64: dts: qcom: qcs615: add the APPS SMMU node
Date: Mon, 28 Oct 2024 16:46:34 +0100 [thread overview]
Message-ID: <828c465f-684b-4257-86cb-d9c753fc30f1@oss.qualcomm.com> (raw)
In-Reply-To: <nhthg2rlfatc2pyhsuoulvo5447cxg7buv4aq3r7r5amsmjjoq@pgfyvvegfron>
On 26.10.2024 8:18 PM, Dmitry Baryshkov wrote:
> On Fri, Oct 25, 2024 at 06:45:01PM +0200, Konrad Dybcio wrote:
>> On 25.10.2024 1:06 PM, Dmitry Baryshkov wrote:
>>> On Fri, Oct 25, 2024 at 10:54:24AM +0200, Konrad Dybcio wrote:
>>>> On 25.10.2024 5:07 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>
>>>>> ---
>>>>
>>>> You probably also want to mark it `dma-coherent` (see e.g.
>>>> x1e80100.dtsi)
>>>
>>> Is it? I don't think SM6150 had dma-coherent SMMU, at least it wasn't
>>> marked as such.
>>
>> I don't think I have any documentation on this, so.. one way to find out!
>
> I don't have qcs615 at hand, so a purely theoretical question. But how
> should it break if we mark it as dma-coherent, while it is not?
The board will hang rather quickly
Konrad
next prev parent reply other threads:[~2024-10-28 15:46 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
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 [this message]
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=828c465f-684b-4257-86cb-d9c753fc30f1@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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=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