Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
To: Sumit Garg <sumit.garg@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	akhilpo@oss.qualcomm.com, dikshita.agarwal@oss.qualcomm.com,
	robin.clark@oss.qualcomm.com, lumag@kernel.org,
	linux-kernel@vger.kernel.org,
	Prakash Gupta <guptap@qti.qualcomm.com>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: agatti: Fix IOMMU DT properties
Date: Fri, 2 Jan 2026 15:32:57 +0530	[thread overview]
Message-ID: <5fdf6122-3c2b-44fb-b8ea-9e554208a56d@oss.qualcomm.com> (raw)
In-Reply-To: <CAGptzHOftKG_3h3KegrYuNiaDFCUHC8oS+eN2JyBDh=aRMod4g@mail.gmail.com>


On 12/29/2025 12:50 PM, Sumit Garg wrote:
> Hey Everyone,
> 
> On Mon, Dec 29, 2025 at 12:37 PM Sumit Garg <sumit.garg@oss.qualcomm.com> wrote:
>>
>> Fix IOMMU DT propeties for GPU, display and video peripherals via
>> dropping SMMU stream IDs which relates to secure context bank.
>>
>> This problem only surfaced when the Gunyah based firmware stack is
>> ported on Agatti replacing the legacy QHEE based firmware stack. Assigning
>> Linux kernel (HLOS) VMID to secure context bank stream IDs is treated
>> as a fault by Gunyah hypervisor which were previously ignored by QHEE
>> hypervisor.
>>
>> The DT changes should be backwards compatible with legacy QHEE based
>> firmware stack too.
>>
>> Suggested-by: Prakash Gupta <guptap@qti.qualcomm.com>
>> Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
>> ---
>>   arch/arm64/boot/dts/qcom/agatti.dtsi | 11 +++--------
>>   1 file changed, 3 insertions(+), 8 deletions(-)
>>
> 
> Looks like I messed up this patch-set with email delivery leading to
> non-delivery. I resent it properly again here [1]. Apologies for the
> noise.
> 
> [1] https://lore.kernel.org/lkml/20251229070712.456138-1-sumit.garg@oss.qualcomm.com/
> 
> -Sumit
> 
>> diff --git a/arch/arm64/boot/dts/qcom/agatti.dtsi b/arch/arm64/boot/dts/qcom/agatti.dtsi
>> index 8bf5c5583fc2..e705eb24160a 100644
>> --- a/arch/arm64/boot/dts/qcom/agatti.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/agatti.dtsi
>> @@ -1613,8 +1613,7 @@ gpu: gpu@5900000 {
>>                                           &bimc SLAVE_EBI1 RPM_ALWAYS_TAG>;
>>                          interconnect-names = "gfx-mem";
>>
>> -                       iommus = <&adreno_smmu 0 1>,
>> -                                <&adreno_smmu 2 0>;
>> +                       iommus = <&adreno_smmu 0 1>;
>>                          operating-points-v2 = <&gpu_opp_table>;
>>                          power-domains = <&rpmpd QCM2290_VDDCX>;
>>                          qcom,gmu = <&gmu_wrapper>;
>> @@ -1895,8 +1894,7 @@ mdss: display-subsystem@5e00000 {
>>
>>                          power-domains = <&dispcc MDSS_GDSC>;
>>
>> -                       iommus = <&apps_smmu 0x420 0x2>,
>> -                                <&apps_smmu 0x421 0x0>;
>> +                       iommus = <&apps_smmu 0x420 0x2>;
>>                          interconnects = <&mmrt_virt MASTER_MDP0 RPM_ALWAYS_TAG
>>                                           &bimc SLAVE_EBI1 RPM_ALWAYS_TAG>,
>>                                          <&bimc MASTER_APPSS_PROC RPM_ALWAYS_TAG
>> @@ -2339,10 +2337,7 @@ venus: video-codec@5a00000 {
>>
>>                          memory-region = <&pil_video_mem>;
>>                          iommus = <&apps_smmu 0x860 0x0>,
>> -                                <&apps_smmu 0x880 0x0>,
>> -                                <&apps_smmu 0x861 0x04>,
>> -                                <&apps_smmu 0x863 0x0>,
>> -                                <&apps_smmu 0x804 0xe0>;
>> +                                <&apps_smmu 0x880 0x0>;

Are you planning to update the binding [1] with this change ? If so, how 
to handle the case of iommus for gunyah based vs non-gunyah based ?

[1] 
https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/media/qcom%2Cqcm2290-venus.yaml#L45

Regards,
Vikash
>>
>>                          interconnects = <&mmnrt_virt MASTER_VIDEO_P0 RPM_ALWAYS_TAG
>>                                           &bimc SLAVE_EBI1 RPM_ALWAYS_TAG>,
>> --
>> 2.51.0
>>


  reply	other threads:[~2026-01-02 10:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29  7:07 [PATCH 1/2] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2025-12-29  7:07 ` [PATCH 2/2] arm64: dts: qcom: agatti: Address Gunyah memory alignment needs Sumit Garg
2025-12-29  7:20 ` [PATCH 1/2] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2026-01-02 10:02   ` Vikash Garodia [this message]
2026-01-02 11:52     ` Sumit Garg
2026-01-05  7:21       ` Vikash Garodia
2026-01-06  2:38         ` Dmitry Baryshkov
2026-01-06  5:42           ` Sumit Garg
  -- strict thread matches above, loose matches on Subject: below --
2025-12-29  7:12 Sumit Garg
2025-12-29 12:41 ` Konrad Dybcio
2025-12-29 20:00 ` Dmitry Baryshkov
2025-12-30  5:15   ` Sumit Garg
2025-12-30  7:05     ` Dmitry Baryshkov
2025-12-30  7:54       ` Sumit Garg
2026-01-03 15:43         ` Bjorn Andersson
2026-01-05  6:27           ` Sumit Garg
2025-12-30 12:46       ` Akhil P Oommen
2025-12-30 14:40         ` Dmitry Baryshkov
2025-12-29 20:39 ` Rob Herring
2025-12-29 21:27 ` Akhil P Oommen

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=5fdf6122-3c2b-44fb-b8ea-9e554208a56d@oss.qualcomm.com \
    --to=vikash.garodia@oss.qualcomm.com \
    --cc=akhilpo@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dikshita.agarwal@oss.qualcomm.com \
    --cc=guptap@qti.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=robh@kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sumit.garg@oss.qualcomm.com \
    /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