On 2025-06-23 17:02, Piotr Oniszczuk wrote:
quoted
Wiadomość napisana przez Alexey Charkov [off-list ref] w dniu 23 cze 2025, o godz. 15:58:
On Mon, Jun 23, 2025 at 1:19 PM Alexey Charkov [off-list ref] wrote:
quoted
Okay, I've bisected this.
TLDR: Linux and u-boot seem to have nothing to do with it, opensource
TF-A doesn't work, binary BL31 starting with v1.09 do not work. BL31
v1.08 and earlier work fine.
v1.09 added support for 1 GHz hrtimer in addition to the normal 24 MHz
rate. Mainline U-Boot may only support use of 24 MHz hrtimer, unsure
what impact the hrtimer rate has. Mixing blobs with/without 1 GHz
support is known to cause issues. At one point the latest rkbin tree may
have contained incompatible rk3576 blobs (mixed 1 ghz vs 24 mhz rate).
Did you try with newer blobs, i.e. ddr init v1.09, bl31 v1.19 blobs [1]
and mainline U-Boot [2] ?
[1] https://github.com/radxa/rkbin/commits/develop-v2025.04/
[2] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commits/rk3576
Regards,
Jonas
just fyi:
to confirm: replacing only bl31 to 1.08 makes all good
with perf gov. clocks staying on 2200/2300
clock estimations are predictable, constant and estimating constantly 2400
ux is „like” on 3588
Alexey: many thx for finding root cause component!