From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: arm-smmu: qcom: add compatible for IPQ9650 SoC
Date: Tue, 4 Aug 2026 12:13:26 +0530 [thread overview]
Message-ID: <c3c01f2e-9070-4603-a5b2-9b404ab2b94d@oss.qualcomm.com> (raw)
In-Reply-To: <20260803-therapeutic-coua-of-judgment-5c6cdf@quoll>
On 8/3/2026 2:54 PM, Krzysztof Kozlowski wrote:
> On Fri, Jul 31, 2026 at 11:01:26AM +0530, Kathiravan Thirumoorthy wrote:
>> Add the compatible string for the APPS SMMU present on the Qualcomm
>> IPQ9650 SoC.
>>
>> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
>> ---
>> Changes in v2:
>> - Add the proper constraints - no clocks needed for IPQ9650
>> - Link to v1: https://patch.msgid.link/20260512-ipq9650_smmu_binding-v1-1-04defdaa140c@oss.qualcomm.com
>>
>> To: Will Deacon <will@kernel.org>
>> To: Robin Murphy <robin.murphy@arm.com>
>> To: "Joerg Roedel (AMD)" <joro@8bytes.org>
>> To: Rob Herring <robh@kernel.org>
>> To: Krzysztof Kozlowski <krzk+dt@kernel.org>
>> To: Conor Dooley <conor+dt@kernel.org>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: iommu@lists.linux.dev
>> Cc: devicetree@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>> Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
>> index f2188942f877..ffa33b7f4a96 100644
>> --- a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
>> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
>> @@ -38,6 +38,7 @@ properties:
>> - qcom,eliza-smmu-500
>> - qcom,glymur-smmu-500
>> - qcom,hawi-smmu-500
>> + - qcom,ipq9650-smmu-500
>> - qcom,kaanapali-smmu-500
>> - qcom,maili-smmu-500
>> - qcom,milos-smmu-500
>> @@ -625,6 +626,7 @@ allOf:
>> - qcom,eliza-smmu-500
>> - qcom,glymur-smmu-500
>> - qcom,hawi-smmu-500
>> + - qcom,ipq9650-smmu-500
> This will disallow clocks also for the Adreno one, so confirm that it
> also does not have clocks.
IPQ9650 doesn't have Adreno IP. Please let me know if I need to explicit
about it in the commit message or this is fine?
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-08-04 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 5:31 [PATCH v2] dt-bindings: arm-smmu: qcom: add compatible for IPQ9650 SoC Kathiravan Thirumoorthy
2026-08-03 9:24 ` Krzysztof Kozlowski
2026-08-04 6:43 ` Kathiravan Thirumoorthy [this message]
2026-08-04 6:44 ` Krzysztof Kozlowski
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=c3c01f2e-9070-4603-a5b2-9b404ab2b94d@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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