From: Heiko Stuebner <heiko@sntech.de>
To: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>,
Alexey Charkov <alchark@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>
Cc: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
XiaoDong Huang <derrick.huang@rock-chips.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: rockchip: list all CPU supplies on ArmSoM Sige5
Date: Mon, 23 Jun 2025 23:17:06 +0200 [thread overview]
Message-ID: <12692993.O9o76ZdvQC@phil> (raw)
In-Reply-To: <90b7a1b6-bc49-414d-9cde-e6fad46d2650@kwiboo.se>
Am Montag, 23. Juni 2025, 23:07:53 Mitteleuropäische Sommerzeit schrieb Jonas Karlman:
> On 2025-06-23 19:40, Jonas Karlman wrote:
> > On 2025-06-23 17:02, Piotr Oniszczuk wrote:
> >>
> >>
> >>> Wiadomość napisana przez Alexey Charkov <alchark@gmail.com> w dniu 23 cze 2025, o godz. 15:58:
> >>>
> >>> On Mon, Jun 23, 2025 at 1:19 PM Alexey Charkov <alchark@gmail.com> wrote:
> >>>>
> >>>>
> >>>
> >>> 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).
>
> Clarification:
> Following boot1 parameter activates use of 1 GHz hrtimer, see [3].
>
> This parameter was added to rkbin repo before all blobs was updated to
> fully support use of the 1 ghz mode, and is the source for incompatible
> blobs I referenced above.
>
> [BOOT1_PARAM]
> WORD_2=0x100
which I guess is something we don't do in u-boot at all right now?
Which would also mean, that something may have broken with the 24MHz mode
when the 1GHz thing was added. And nobody ever realized that because the
Rockchip thing uses that boot param for all of them?
>
> [3] https://github.com/rockchip-linux/rkbin/commit/cbbc6868221fb416d4f0d86a10e493dbbbc1f117
>
> Regards,
> Jonas
>
> >
> > 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!
> >>
> >>
> >
>
>
next prev parent reply other threads:[~2025-06-24 0:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 17:01 [PATCH 0/4] arm64: dts: rockchip: enable further peripherals on ArmSoM Sige5 Alexey Charkov
2025-06-03 17:01 ` [PATCH 1/4] arm64: dts: rockchip: list all CPU supplies " Alexey Charkov
2025-06-04 18:38 ` Nicolas Frattaroli
2025-06-04 19:12 ` Alexey Charkov
2025-06-04 19:23 ` Nicolas Frattaroli
2025-06-04 19:54 ` Alexey Charkov
2025-06-05 13:22 ` Piotr Oniszczuk
2025-06-05 13:42 ` Alexey Charkov
2025-06-08 7:24 ` Piotr Oniszczuk
2025-06-09 14:05 ` Alexey Charkov
2025-06-15 15:59 ` Piotr Oniszczuk
2025-06-15 16:20 ` Alexey Charkov
2025-06-18 13:51 ` Alexey Charkov
2025-06-18 14:06 ` Nicolas Frattaroli
2025-06-18 14:48 ` Alexey Charkov
2025-06-20 16:02 ` Alexey Charkov
2025-06-21 19:35 ` Alexey Charkov
2025-06-21 19:44 ` Heiko Stuebner
2025-06-21 21:21 ` Alexey Charkov
2025-06-22 13:48 ` Heiko Stuebner
2025-06-23 9:19 ` Alexey Charkov
2025-06-23 13:58 ` Alexey Charkov
2025-06-23 15:02 ` Piotr Oniszczuk
2025-06-23 17:40 ` Jonas Karlman
2025-06-23 21:07 ` Jonas Karlman
2025-06-23 21:17 ` Heiko Stuebner [this message]
2025-06-24 7:41 ` Alexey Charkov
2025-06-23 18:04 ` Jonas Karlman
2025-06-05 11:17 ` Diederik de Haas
2025-06-05 11:23 ` Alexey Charkov
2025-06-03 17:01 ` [PATCH 2/4] arm64: dts: rockchip: enable USB A ports " Alexey Charkov
2025-06-03 17:51 ` Nicolas Frattaroli
2025-06-04 6:52 ` Alexey Charkov
2025-06-04 13:24 ` Nicolas Frattaroli
2025-06-03 17:01 ` [PATCH 3/4] arm64: dts: rockchip: enable wifi " Alexey Charkov
2025-06-04 19:01 ` Nicolas Frattaroli
2025-06-04 19:48 ` Alexey Charkov
2025-06-05 2:43 ` Jimmy Hon
2025-06-05 6:32 ` Alexey Charkov
2025-06-05 14:14 ` Alexey Charkov
2025-06-07 2:42 ` Jimmy Hon
2025-06-03 17:01 ` [PATCH 4/4] arm64: dts: rockchip: enable bluetooth " Alexey Charkov
2025-06-04 13:58 ` [PATCH 0/4] arm64: dts: rockchip: enable further peripherals " Rob Herring (Arm)
2025-06-04 14:15 ` Alexey Charkov
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=12692993.O9o76ZdvQC@phil \
--to=heiko@sntech.de \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=derrick.huang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=piotr.oniszczuk@gmail.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).