public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@kernel.org>
To: Konrad Dybcio <konrad.dybcio@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>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: agatti: Address Gunyah memory alignment needs
Date: Tue, 30 Dec 2025 10:16:52 +0530	[thread overview]
Message-ID: <aVNZPOHHZn2U5N_R@sumit-xelite> (raw)
In-Reply-To: <90264256-f53d-4a12-9b37-4cc43720c181@oss.qualcomm.com>

On Mon, Dec 29, 2025 at 01:43:18PM +0100, Konrad Dybcio wrote:
> On 12/29/25 8:12 AM, Sumit Garg wrote:
> > From: Sumit Garg <sumit.garg@oss.qualcomm.com>
> > 
> > Gunyah hypervisor requires it's memory start address to be 2MB aligned.
> > So the address map for Agatti is updated to incorporate that requirement.
> > This should be a backwards compatible DT change which should work with
> > legacy QHEE based firmware stack too.
> > 
> > Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> > ---
> >  arch/arm64/boot/dts/qcom/agatti.dtsi | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm64/boot/dts/qcom/agatti.dtsi b/arch/arm64/boot/dts/qcom/agatti.dtsi
> > index e705eb24160a..153916980ac0 100644
> > --- a/arch/arm64/boot/dts/qcom/agatti.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/agatti.dtsi
> > @@ -298,8 +298,8 @@ reserved_memory: reserved-memory {
> >  		#size-cells = <2>;
> >  		ranges;
> >  
> > -		hyp_mem: hyp@45700000 {
> > -			reg = <0x0 0x45700000 0x0 0x600000>;
> > +		hyp_mem: hyp@45600000 {
> > +			reg = <0x0 0x45600000 0x0 0x700000>;
> 
> On a second thought, please add a comment like:
> 
> /* Gunyah requires the start of the region to be 2MiB-aligned, QHEE doesn't care */
> 
> to prevent someone "fixing" it in the future

Sounds reasonable, I will add this comment on the next spin. I hope that
I can keep you review tag with comment added.

-Sumit

  reply	other threads:[~2025-12-30  4:47 UTC|newest]

Thread overview: 24+ 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 [this message]
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
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:07 ` [PATCH 2/2] arm64: dts: qcom: agatti: Address Gunyah memory alignment needs 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=aVNZPOHHZn2U5N_R@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=konrad.dybcio@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=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