public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@kernel.org>
To: 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, vikash.garodia@oss.qualcomm.com,
	dikshita.agarwal@oss.qualcomm.com, robin.clark@oss.qualcomm.com,
	lumag@kernel.org, loic.poulain@oss.qualcomm.com,
	jorge.ramirez@oss.qualcomm.com, linux-kernel@vger.kernel.org,
	Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: [PATCH v2 0/3] arm64: dts: qcom: agatti: Fix IOMMU DT properties
Date: Fri, 16 Jan 2026 11:50:01 +0530	[thread overview]
Message-ID: <20260116062004.237356-1-sumit.garg@kernel.org> (raw)

From: Sumit Garg <sumit.garg@oss.qualcomm.com>

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.

Changes in v2:
---
- Dropped Gunyah related reserved memory requirement changes
- Added DT bindings changes related to IOMMU property fixups
- Collected review tags for the DT changes

Sumit Garg (3):
  dt-bindings: display: msm: qcm2290-mdss: Fix iommus property
  dt-bindings: media: venus: Fix iommus property
  arm64: dts: qcom: agatti: Fix IOMMU DT properties

 .../bindings/display/msm/qcom,qcm2290-mdss.yaml       |  5 ++---
 .../devicetree/bindings/media/qcom,qcm2290-venus.yaml |  6 ++----
 arch/arm64/boot/dts/qcom/agatti.dtsi                  | 11 +++--------
 3 files changed, 7 insertions(+), 15 deletions(-)

-- 
2.51.0


             reply	other threads:[~2026-01-16  6:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  6:20 Sumit Garg [this message]
2026-01-16  6:20 ` [PATCH v2 1/3] dt-bindings: display: msm: qcm2290-mdss: Fix iommus property Sumit Garg
2026-01-16  8:46   ` Krzysztof Kozlowski
2026-01-16 12:53     ` Sumit Garg
2026-01-16 13:15       ` Krzysztof Kozlowski
2026-01-20 12:16         ` Sumit Garg
2026-01-20 12:30           ` Krzysztof Kozlowski
2026-01-21  7:59             ` Sumit Garg
2026-01-16  6:20 ` [PATCH v2 2/3] media: dt-bindings: venus: " Sumit Garg
2026-01-16  8:47   ` Krzysztof Kozlowski
2026-01-16  6:20 ` [PATCH v2 3/3] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2026-01-16  8:40   ` Dmitry Baryshkov

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=20260116062004.237356-1-sumit.garg@kernel.org \
    --to=sumit.garg@kernel.org \
    --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=jorge.ramirez@oss.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=loic.poulain@oss.qualcomm.com \
    --cc=lumag@kernel.org \
    --cc=robh@kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sumit.garg@oss.qualcomm.com \
    --cc=vikash.garodia@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