mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Ahmad Fatoum" <a.fatoum@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/3] ARM: rockchip: pack the device tree passed to TF-A and OP-TEE
Date: Thu, 15 Oct 2026 08:00:01 +0000	[thread overview]
Message-ID: <03ae4cf2-8f46-438e-95fe-3c966544b101@pengutronix.de> (raw)
In-Reply-To: <213681da-7e7c-4856-a383-670d2e9368a1@pengutronix.de>

On 2026-10-14 14:45, Ahmad Fatoum wrote:
> Hello Sascha,
> 
> On 10/1/26 9:42 AM, Sascha Hauer wrote:
> > rockchip_create_optee_fdt() builds a device tree with just the memory
> > nodes, but fdt_create_empty_tree() sets its totalsize to the size of the
> > whole scratch buffer, i.e. CONFIG_ARCH_ROCKCHIP_ATF_FDT_SIZE (384 KiB).
> > 
> > TF-A and OP-TEE both call fdt_open_into() on the device tree, which
> > copies totalsize bytes regardless of the actual content. TF-A does this
> > with the MMU disabled and OP-TEE through an uncached mapping. On an
> > RK3588 this takes 185 ms in TF-A and another 182 ms in OP-TEE.
> > 
> > Pack the device tree so that totalsize matches its content. OP-TEE can
> > still expand it in place, the scratch buffer keeps its size.
> 
> While I don't object to the patch, for future reference it would be good
> to point out what the implication is for fixups onto the device tree.
> 
> Do both TF-A and OP-TEE apply fixups on this platforms? Are these fixups
> no longer possible now?

TF-A doesn't apply any fixups. OP-TEE does, but it opens the device tree
with fdt_open_into(blob, blob, CFG_DTB_MAX_SIZE), so it can expand as
necessary up to CFG_DTB_MAX_SIZE. It just doesn't have to read so much
from it initially.

Sascha

--
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2026-10-15  8:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  7:42 [PATCH 0/3] Rockchip: early boot time optimization Sascha Hauer
2026-10-01  7:42 ` [PATCH 1/3] ARM: rockchip: move to the load address with the MMU enabled Sascha Hauer
2026-10-01  7:42 ` [PATCH 2/3] ARM: rockchip: boards: leave moving to the load address to atf.c Sascha Hauer
2026-10-01  8:30   ` Ahmad Fatoum
2026-10-01 10:19     ` Sascha Hauer
2026-10-01  7:42 ` [PATCH 3/3] ARM: rockchip: pack the device tree passed to TF-A and OP-TEE Sascha Hauer
2026-10-14 12:45   ` Ahmad Fatoum
2026-10-15  8:00     ` Sascha Hauer [this message]
2026-10-06  6:41 ` [PATCH 0/3] Rockchip: early boot time optimization Sascha Hauer

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=03ae4cf2-8f46-438e-95fe-3c966544b101@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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