mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Romli, Khairul Anuar" <khairul.anuar.romli@altera.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Rao, Mahesh" <mahesh.rao@altera.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Ng, Adrian Ho Yin" <adrian.ho.yin.ng@altera.com>,
	"Rabara, Niravkumar Laxmidas" <nirav.rabara@altera.com>
Subject: Re: [PATCH v5 2/2] arm64: dts: intel: Add Agilex5 SVC node with memory region
Date: Wed, 5 Nov 2025 08:55:18 +0000	[thread overview]
Message-ID: <9e24ca8b-6c05-43ba-a7ce-98886ef6db31@altera.com> (raw)
In-Reply-To: <20251105-flying-asp-of-poetry-cd9d2e@kuoka>

On 5/11/2025 4:25 pm, Krzysztof Kozlowski wrote:
> On Wed, Nov 05, 2025 at 10:28:02AM +0800, Khairul Anuar Romli wrote:
>> Introduce the Stratix10 SoC Service Layer (SVC) node for Agilex5 SoCs. This
>> node includes the compatible string "intel,agilex5-svc" and references a
>> reserved memory region used for communication with the Secure Device
>> Manager (SDM).
>>
>> Agilex5 introduces changes in how reserved memory is mapped and accessed
>> compared to previous SoC generations, particularly with the addition of
>> IOMMU support. Unlike earlier platforms, Agilex5 enables the use of the
>> Translation Buffer Unit (TBU) in non-secure mode, allowing Linux to access
>> it through the IOMMU framework. This commit updates the device tree
>> structure to support Agilex5-specific handling of the SVC interface,
>> including the necessary bindings for IOMMU integration.
>>
>> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
>> ---
>> Changes in v5:
>> 	- No change.
>> Changes in v4:
>> 	- Exclude peers reviewers in the sign off.
>> Changes in v3:
>> 	- include iommu property in svc node.
>> 	- Rephrase git commit message to describe iommu presence
>> 	  in Agilex5
>> Changes in v2:
>> 	- Rephrase commit message to exclude mentioning iommu
>> ---
>>   arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi b/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
>> index a13ccee3c4c3..15284092897e 100644
>> --- a/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
>> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
>> @@ -841,5 +841,14 @@ queue7 {
>>   				};
>>   			};
>>   		};
>> +
>> +		firmware {
> 
> Did you just add node to the end of the file? No. Place it somewhere
> after cpus, see DTS coding style.
> 
Noted. I will place this node after cpu to make it consistent with 
Agilex dts.
> Another problem that you have here warnings, which tools would tell you.
> Please use tools instead of humans, see maintainer soc profiles (both)
> for more explanation.
>
I use make DTC_FLAGS=-@ intel/socfpga_agilex5_socdk.dtb to check for the 
warning but my thought was those are not related. Now I test again 
without the firmware the changes and run the build command, I do see it 
is clean without the changes.

I will fix this one and ensure the build is warning free.

Thanks.

Regards,
Khairul
> Best regards,
> Krzysztof
> 


      reply	other threads:[~2025-11-05  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  2:28 [PATCH v5 0/2] Enable Service layer driver for Agilex5 Khairul Anuar Romli
2025-11-05  2:28 ` [PATCH v5 1/2] dt-bindings: firmware: svc: Add IOMMU support " Khairul Anuar Romli
2025-11-05  8:23   ` Krzysztof Kozlowski
2025-11-05  8:36     ` Romli, Khairul Anuar
2025-11-05  2:28 ` [PATCH v5 2/2] arm64: dts: intel: Add Agilex5 SVC node with memory region Khairul Anuar Romli
2025-11-05  8:25   ` Krzysztof Kozlowski
2025-11-05  8:55     ` Romli, Khairul Anuar [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=9e24ca8b-6c05-43ba-a7ce-98886ef6db31@altera.com \
    --to=khairul.anuar.romli@altera.com \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh.rao@altera.com \
    --cc=nirav.rabara@altera.com \
    --cc=robh@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

all inboxes | Powered by JetHome®