From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Robin Murphy <Robin.Murphy@arm.com>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm-smmu: qcom:: Fix Hawi compatible placement
Date: Wed, 22 Apr 2026 16:37:03 +0200 [thread overview]
Message-ID: <42e86a47-fbcf-4964-8dda-acfd1dfab53e@kernel.org> (raw)
In-Reply-To: <20260422142710.2f6f2oijbsjojbmi@hu-mojha-hyd.qualcomm.com>
On 22/04/2026 16:27, Mukesh Ojha wrote:
>>> - enum:
>>> - qcom,eliza-smmu-500
>>> - qcom,glymur-smmu-500
>>> + - qcom,hawi-smmu-500
>>> - qcom,kaanapali-smmu-500
>>> - qcom,milos-smmu-500
>>> - qcom,qcm2290-smmu-500
>>> @@ -93,7 +94,6 @@ properties:
>>> items:
>>> - enum:
>>> - qcom,glymur-smmu-500
>>> - - qcom,hawi-smmu-500
>>
>> No, why? That's for GPU. Why are you moving GPU compatible to non-GPU place?
>
> Earlier commit was meant for CPUs and not for GPUs, hence moving it Or,
OK, but:
> Are you saying do not do the movement and add one for CPUs ?
yeah, because you might need it in this place for the GPU. Therefore I
would propose to check what compatible you expect for the GPU part and
just add it.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-04-22 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 8:33 [PATCH] dt-bindings: arm-smmu: qcom:: Fix Hawi compatible placement Mukesh Ojha
2026-04-22 9:04 ` Krzysztof Kozlowski
2026-04-22 14:27 ` Mukesh Ojha
2026-04-22 14:37 ` Krzysztof Kozlowski [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=42e86a47-fbcf-4964-8dda-acfd1dfab53e@kernel.org \
--to=krzk@kernel.org \
--cc=Robin.Murphy@arm.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=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=robh@kernel.org \
--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