mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Khairul Anuar Romli <khairul.anuar.romli@altera.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Mahesh Rao <mahesh.rao@altera.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: firmware: svc: Add IOMMU support for Agilex5
Date: Fri, 7 Nov 2025 05:44:58 -0600	[thread overview]
Message-ID: <c8a32a8b-f37f-44b3-ac31-7f6d6f608dd2@kernel.org> (raw)
In-Reply-To: <dc40029c970d33b433e763202e6622a0a2f12d72.1762387665.git.khairul.anuar.romli@altera.com>



On 11/6/25 17:35, Khairul Anuar Romli wrote:
> In Agilex5, the TBU (Translation Buffer Unit) can now operate in non-secure
> mode, enabling Linux to utilize it through the IOMMU framework. This allows
> improved memory management capabilities in non-secure environments. With
> Agilex5 lifting this restriction, we are now extending the device tree
> bindings to support IOMMU for the Agilex5 SVC.
> 
> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
> ---
> Changes in v6:
> 	- Reinstate AllOf to avoid re-indentation on future addition to
> 	  the logical condition.
> Changes in v6:
> 	- Use contains enum instead of const

This should be v5. Krzysztof gave you his Reviewed-by: in v5, you should 
include his Reviewed-by: in this version.

Dinh

  parent reply	other threads:[~2025-11-07 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 23:35 [PATCH v6 0/2] Enable Service layer driver " Khairul Anuar Romli
2025-11-06 23:35 ` [PATCH v6 1/2] dt-bindings: firmware: svc: Add IOMMU support " Khairul Anuar Romli
2025-11-07  7:35   ` Krzysztof Kozlowski
2025-11-07  7:49     ` Romli, Khairul Anuar
2025-11-07 11:44   ` Dinh Nguyen [this message]
2025-11-06 23:35 ` [PATCH v6 2/2] arm64: dts: intel: Add Agilex5 SVC node with memory region Khairul Anuar Romli

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=c8a32a8b-f37f-44b3-ac31-7f6d6f608dd2@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khairul.anuar.romli@altera.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh.rao@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®