public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	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, linux-kernel@vger.kernel.org,
	Sumit Garg <sumit.garg@oss.qualcomm.com>,
	Prakash Gupta <guptap@qti.qualcomm.com>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: agatti: Fix IOMMU DT properties
Date: Tue, 30 Dec 2025 10:45:38 +0530	[thread overview]
Message-ID: <aVNf-lZ1KcH3tRV_@sumit-xelite> (raw)
In-Reply-To: <bylruidduy2u4lsqlhzmohahgkm633hijffi3s2wt5ojeaotk3@awulzz2qdg7h>

On Mon, Dec 29, 2025 at 10:00:02PM +0200, Dmitry Baryshkov wrote:
> On Mon, Dec 29, 2025 at 12:42:57PM +0530, Sumit Garg wrote:
> > 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.
> 
> We are porting the underlaying layer. Can we make it to behave in a way
> similar to the _existing_ software? If DT was a part of the firmware, it
> would have been fine to perform such updates. But as it is not, we
> really should try not to break the interface boundary between firmware
> and the kernel.

I support your viewpoint. But in this current case Linux kernel VMID mapping
for secure context bank stream IDs is incorrect. As Konrad mentioned in the
other thread that for secure media streaming use-cases, it rather requires
proper representation via iommu-map such that appropriate VMID can be mapped.

> 
> I'm fine with the change, but I think we should make sure that Gunyah
> doesn't break existing device trees.

Sure, this change isn't breaking any DT ABI but brings compliance to
usage of stream IDs.

-Sumit

> 
> > 
> > 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(-)
> > 
> 
> -- 
> With best wishes
> Dmitry
> 

  reply	other threads:[~2025-12-30  5:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29  7:12 [PATCH 1/2] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2025-12-29  7:12 ` [PATCH 2/2] arm64: dts: qcom: agatti: Address Gunyah memory alignment needs Sumit Garg
2025-12-29 12:42   ` Konrad Dybcio
2025-12-29 12:43   ` Konrad Dybcio
2025-12-30  4:46     ` Sumit Garg
2025-12-30 13:07       ` Konrad Dybcio
2026-01-03 15:49   ` Bjorn Andersson
2026-01-05  5:46     ` Sumit Garg
2026-01-07 11:29       ` Konrad Dybcio
2026-01-08 10:50         ` Sumit Garg
2026-01-08 12:43           ` Konrad Dybcio
2026-01-09 10:07             ` Sumit Garg
2025-12-29 12:41 ` [PATCH 1/2] arm64: dts: qcom: agatti: Fix IOMMU DT properties Konrad Dybcio
2025-12-29 20:00 ` Dmitry Baryshkov
2025-12-30  5:15   ` Sumit Garg [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2025-12-29  7:07 Sumit Garg
2025-12-29  7:20 ` Sumit Garg
2026-01-02 10:02   ` Vikash Garodia
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

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=aVNf-lZ1KcH3tRV_@sumit-xelite \
    --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=dmitry.baryshkov@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 \
    --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