From: Quentin Schulz <quentin.schulz@cherry.de>
To: Chris Morgan <macroalpha82@gmail.com>,
linux-rockchip@lists.infradead.org
Cc: devicetree@vger.kernel.org, sebastian.reichel@collabora.com,
heiko@sntech.de, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: remove rk3588 optee node
Date: Fri, 31 Jan 2025 17:46:20 +0100 [thread overview]
Message-ID: <5d0ae245-1ad3-4e3c-9c68-28babc7290a6@cherry.de> (raw)
In-Reply-To: <20250130181005.6319-1-macroalpha82@gmail.com>
Hi Chris,
On 1/30/25 7:10 PM, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Remove Optee node from rk3588 devicetree. When Optee is present and
> used the node will be added automatically by U-Boot when
> CONFIG_OPTEE_LIB=y and CONFIG_SPL_ATF_NO_PLATFORM_PARAM is not set.
This is too big to ask for right now, 100% of the RK3588 products in
upstream U-Boot have CONFIG_SPL_ATF_NO_PLATFORM_PARAM set.
Does it hurt to keep it forever?
> When Optee is not present or used, the node will trigger a probe
> that generates a (harmless) message on the kernel log.
>
And what if we have OP-TEE without this node present, which would be
possible if we have CONFIG_SPL_ATF_NO_PLATFORM_PARAM set in U-Boot?
I guess we could detect from U-Boot if a TEE is loaded as part of
u-boot.itb and fixup the DTB otherwise to mark this node as status =
"disabled"?
Cheers,
Quentin
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-01-31 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 18:10 [PATCH] arm64: dts: rockchip: remove rk3588 optee node Chris Morgan
2025-01-31 16:46 ` Quentin Schulz [this message]
2025-01-31 16:59 ` Chris Morgan
2025-02-03 16:32 ` Quentin Schulz
2025-02-03 21:27 ` Chris Morgan
2025-02-04 9:12 ` Quentin Schulz
2025-02-04 16:16 ` Chris Morgan
2025-02-10 10:20 ` Heiko Stübner
2025-02-10 17:06 ` Chris Morgan
2025-02-11 12:58 ` Quentin Schulz
2025-02-11 20:35 ` Heiko Stuebner
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=5d0ae245-1ad3-4e3c-9c68-28babc7290a6@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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