From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: rockchip: atf: move PBL malloc space away from OP-TEE memory
Date: Wed, 27 May 2026 14:23:11 +0200 [thread overview]
Message-ID: <0a9c9c04-554b-43eb-b0f5-ed95c8b2b1ed@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvRjaZkARSPnFJBbS8znVPBLJV6SCUFRmOBaa94P_0Vkbg@mail.gmail.com>
Hi,
On 5/26/26 8:40 PM, Alexander Shiyan wrote:
> Ping
See the series I should Cc'd you on.
Would be cool if you could test master with it applied.
Given that June is right around the corner, we would aim for an early
june release that contains the fix.
Cheers,
Ahmad
>
> чт, 21 мая 2026 г. в 12:17, Sascha Hauer <s.hauer@pengutronix.de>:
>>
>> We recently introduced initializing the PBL early memory pool which
>> might be needed for decompressing the BL31/BL32 firmware files. We
>> used the end of the first DRAM region for the pool and with this we
>> ended up exactly in the default OP-TEE memory region which is mapped
>> as faulting. Move the pool directly beneath the OP-TEE memory.
>>
>> Fixes: 76b1f31275 ("ARM: rockchip: initialize PBL malloc")
>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>> ---
>> arch/arm/mach-rockchip/atf.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mach-rockchip/atf.c b/arch/arm/mach-rockchip/atf.c
>> index 14797a1e06..96a891847b 100644
>> --- a/arch/arm/mach-rockchip/atf.c
>> +++ b/arch/arm/mach-rockchip/atf.c
>> @@ -173,7 +173,8 @@ static void rockchip_atf_load_bl31(void *fdt)
>> unsigned long bl31_ep;
>>
>> mmu_early_enable(membase[0], memsize[0]);
>> - pbl_malloc_init(membase[0] + memsize[0] - PBL_MALLOC_SIZE, PBL_MALLOC_SIZE);
>> + pbl_malloc_init(membase[0] + memsize[0] - OPTEE_SIZE - PBL_MALLOC_SIZE,
>> + PBL_MALLOC_SIZE);
>>
>> bl31_ep = load_elf64_image_phdr(&bl31);
>>
>> --
>> 2.47.3
>>
>
>
--
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 |
prev parent reply other threads:[~2026-05-27 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 9:17 Sascha Hauer
2026-05-21 9:27 ` Ahmad Fatoum
2026-05-21 11:19 ` Sascha Hauer
2026-05-26 18:40 ` Alexander Shiyan
2026-05-27 12:23 ` Ahmad Fatoum [this message]
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=0a9c9c04-554b-43eb-b0f5-ed95c8b2b1ed@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
--cc=s.hauer@pengutronix.de \
/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