Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
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>,
	<quic_gurus@quicinc.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 2/4] dt-bindings: arm-smmu: Document Qualcomm QCS615 apps smmu
Date: Mon, 14 Oct 2024 11:09:53 +0800	[thread overview]
Message-ID: <2224b2fe-4e72-4371-9f0b-d5ee211c2210@quicinc.com> (raw)
In-Reply-To: <af81be27-fdfa-4dec-a18c-56c7022e3c75@kernel.org>



在 10/11/2024 2:48 PM, Krzysztof Kozlowski 写道:
> On 11/10/2024 08:31, Qingqing Zhou wrote:
>> Add devicetree binding for apps smmu on Qualcomm QCS615 SoC. SMMU function
>> is required by multiple functions including USB/UFS/Ethernet.
> 
> Do not explain what SMMU is, because it is obvious, but explain how this
> hardware differs from everything existing.
OK, will improve the comments in next patch version.
> 
>>
>> Signed-off-by: Qingqing Zhou <quic_qqzhou@quicinc.com>
>> ---
>>  Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
>> index 92d350b8e01a..9e62c2cdda08 100644
>> --- a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
>> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
>> @@ -36,6 +36,7 @@ properties:
>>          items:
>>            - enum:
>>                - qcom,qcm2290-smmu-500
>> +              - qcom,qcs615-smmu-500
> 
> This is incomplete? No clocks? No power-domains?
This is APPS SMMU, no clocks and no power-domains are needed for DT.
> 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2024-10-14  3:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  6:31 [PATCH 0/4] Add support for APPS SMMU on QCS615 Qingqing Zhou
2024-10-11  6:31 ` [PATCH 1/4] dt-bindings: firmware: qcom,scm: document SCM " Qingqing Zhou
2024-10-11  6:48   ` Krzysztof Kozlowski
2024-10-11  6:31 ` [PATCH 2/4] dt-bindings: arm-smmu: Document Qualcomm QCS615 apps smmu Qingqing Zhou
2024-10-11  6:48   ` Krzysztof Kozlowski
2024-10-14  3:09     ` Qingqing Zhou [this message]
2024-10-14  6:52       ` Krzysztof Kozlowski
2024-10-14  9:53         ` Qingqing Zhou
2024-10-11  6:31 ` [PATCH 3/4] arm64: dts: qcom: qcs615: add scm node Qingqing Zhou
2024-10-11  6:31 ` [PATCH 4/4] arm64: dts: qcom: qcs615: add the APPS SMMU node 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=2224b2fe-4e72-4371-9f0b-d5ee211c2210@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=quic_gurus@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