From: Krzysztof Kozlowski <krzk@kernel.org>
To: muhammad.nazim.amirul.nazle.asmade@altera.com, dinguyen@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] arm64: dts: socfpga: agilex5: Enable the SMMU
Date: Thu, 4 Jun 2026 13:16:38 +0200 [thread overview]
Message-ID: <2d196c4a-911e-43d7-a70b-c0666788dda7@kernel.org> (raw)
In-Reply-To: <20260604105020.24782-2-muhammad.nazim.amirul.nazle.asmade@altera.com>
On 04/06/2026 12:50, muhammad.nazim.amirul.nazle.asmade@altera.com wrote:
> From: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
>
> The SMMU is disabled in socfpga_agilex5.dtsi. The SoC uses a different
> memory-mapped base address for its peripherals, which requires the SMMU
> to be active so that the Secure Device Manager (SDM) can correctly
> access those regions through address translation.
>
> Signed-off-by: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
> ---
> Changes in v3:
> - Fix commit header to follow subsystem naming convention
> - Remove commit body line that restated the subject
> - Clarify which file had the SMMU disabled
>
> Changes in v2:
> - Move SMMU enable into the base DTSI file instead of individual DTS files
> ---
> arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi b/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
> index b06c6d5d60ee..64f3739a0c33 100644
> --- a/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
> @@ -385,7 +385,7 @@ smmu: iommu@16000000 {
> interrupt-names = "eventq", "gerror", "priq";
> dma-coherent;
> #iommu-cells = <1>;
> - status = "disabled";
> + status = "okay";
NAK. Nothing improved and you gave me exactly MINUS 5 minutes to reply
to your comment. You FIRST sent v3 and then 5 minutes later you replied
to my comment. So I should go back in time? How do you imagine this
process working?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-04 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 10:50 [PATCH v3 0/2] arm64: dts: socfpga: Enable SMMU and add DMA coherency for XGMAC muhammad.nazim.amirul.nazle.asmade
2026-06-04 10:50 ` [PATCH v3 1/2] arm64: dts: socfpga: agilex5: Enable the SMMU muhammad.nazim.amirul.nazle.asmade
2026-06-04 11:16 ` Krzysztof Kozlowski [this message]
2026-06-04 10:50 ` [PATCH v3 2/2] arm64: dts: socfpga: agilex5: Add dma-coherent to XGMAC nodes muhammad.nazim.amirul.nazle.asmade
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=2d196c4a-911e-43d7-a70b-c0666788dda7@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muhammad.nazim.amirul.nazle.asmade@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®