From: Michal Simek <michal.simek@amd.com>
To: Tomas Melin <tomas.melin@vaisala.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "arm64: zynqmp: Add an OP-TEE node to the device tree"
Date: Tue, 25 Nov 2025 11:30:35 +0100 [thread overview]
Message-ID: <88b72343-e86f-4b13-adcc-ba09683eb898@amd.com> (raw)
In-Reply-To: <20251125-revert-zynqmp-optee-v1-1-d2ce4c0fcaf6@vaisala.com>
On 11/25/25 08:53, Tomas Melin wrote:
> This reverts commit 06d22ed6b6635b17551f386b50bb5aaff9b75fbe.
>
> OP-TEE logic in U-Boot automatically injects a reserved-memory
> node along with optee firmware node to kernel device tree.
> The injection logic is dependent on that there is no manually
> defined optee node. Having the node in zynqmp.dtsi effectively
> breaks OP-TEE's insertion of the reserved-memory node, causing
> memory access violations during runtime.
>
> Signed-off-by: Tomas Melin <tomas.melin@vaisala.com>
> ---
> For further information about the U-Boot logic related
> to this, see lib/optee/optee.c in U-Boot repository.
What's the behavior with EDK2?
U-Boot also have optee driver. How is it probed when you remove this node?
Thanks,
Michal
next prev parent reply other threads:[~2025-11-25 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:53 [PATCH] Revert "arm64: zynqmp: Add an OP-TEE node to the device tree" Tomas Melin
2025-11-25 10:30 ` Michal Simek [this message]
2025-11-25 11:42 ` Tomas Melin
2025-12-12 12:09 ` Tomas Melin
2025-12-15 15:21 ` Michal Simek
2025-12-15 15:43 ` Tomas Melin
2025-12-15 16:10 ` Michal Simek
2025-12-16 7:00 ` Tomas Melin
2025-12-16 7:12 ` Michal Simek
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=88b72343-e86f-4b13-adcc-ba09683eb898@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tomas.melin@vaisala.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.