From: "Hüseyin BIYIK" <boogiepop@gmx.com>
To: Igor Paunovic <royalnet026@gmail.com>
Cc: Nicolas Dufresne <nicolas@ndufresne.ca>,
Tomeu Vizoso <tomeu@tomeuvizoso.net>,
Heiko Stuebner <heiko@sntech.de>,
Jiaxing Hu <gahing@gahingwoo.com>,
Oded Gabbay <ogabbay@kernel.org>,
dri-devel@lists.freedesktop.org, Jonas Karlman <jonas@kwiboo.se>,
linux-rockchip@lists.infradead.org
Subject: Re: [RFC] accel/rocket: DVFS on RK3588 - a hardware constraint, and some numbers
Date: Wed, 19 Aug 2026 22:07:55 +0200 [thread overview]
Message-ID: <f5241666-9657-4f49-958f-476fd366e408@gmx.com> (raw)
In-Reply-To: <20260819184807.6665-1-royalnet026@gmail.com>
Hello Igor
On 8/19/26 20:48, Igor Paunovic wrote:
> So a question for you and for Hüseyin (added to Cc): is that
> STATUS register perhaps readable from EL3 only, with EL1 reads as
> zero? That would explain everything, since [3] reads it inside the
> firmware. If so, the clean path is the one [3] already implements -
> after my trip I will cherry-pick it into the BL31 my board runs (it is
> plain upstream v2.12 there) and re-measure through plain clk_get_rate,
> which also spares the kernel any GRF access at all.
No you can even read them from userspace with mmap. i think there is
also a firewall configuration where you can restrict the access per ip
core, but default configuration should not require any EL escalation.
If the status register is providing 0, most likely it is not started (i
am guessing by past experience).
Here are the most relevant registers:
GRF.CON0_L.start = 1; // start the status counter
GRF.CON0_L.en = 1; // enable PTVPLL
GRF.CON0_L.osc_ring_sel = n // ring to use
GRF.CON0_H.ring_sel_len = k // length of the ring
GRF.CAL_CNT = 24 // how many sample to average
Result is in:
GRF.STATUS0.OSC_CNT = ...
You can also mess around with this mmm userspace tool where you can edit
the GRF registers visually in an easy way, the python code also shows
how registers interact with each other when clock is calculated if you
want to dig in deeper:
https://github.com/hbiyik/mmm
Here is a quick tutorial i had written on how to observe the PVTPLL
status using mmm.
https://forum.radxa.com/t/mmm-memory-map-manipulator-perfect-tool-to-un-break-your-soc/15332/6
I hope sharing links is fine in mailing list.
Hüseyin
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-08-19 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 13:16 [RFC] accel/rocket: DVFS on RK3588 - a hardware constraint, and some numbers Igor Paunovic
2026-08-01 19:32 ` Jiaxing Hu
2026-08-02 12:04 ` Igor Paunovic
2026-08-15 18:24 ` Tomeu Vizoso
2026-08-17 18:22 ` Nicolas Dufresne
2026-08-18 7:27 ` Igor Paunovic
2026-08-18 12:12 ` Jonas Karlman
2026-08-18 12:30 ` Jonas Karlman
2026-08-19 5:52 ` Igor Paunovic
2026-08-19 9:40 ` Jonas Karlman
2026-08-19 12:59 ` Igor Paunovic
2026-08-19 16:20 ` Jonas Karlman
2026-08-19 18:48 ` Igor Paunovic
2026-08-19 20:07 ` Hüseyin BIYIK [this message]
2026-08-19 18:47 ` Nicolas Dufresne
[not found] <DKDOBW9CJ2Y3.10EEIZDTXPYJZ@cknow-tech.com>
2026-08-01 14:40 ` Igor Paunovic
2026-08-01 16:29 ` Diederik de Haas
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=f5241666-9657-4f49-958f-476fd366e408@gmx.com \
--to=boogiepop@gmx.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gahing@gahingwoo.com \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas@ndufresne.ca \
--cc=ogabbay@kernel.org \
--cc=royalnet026@gmail.com \
--cc=tomeu@tomeuvizoso.net \
/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