Difference between revisions of "Overclocking"

From PINE64
Jump to navigation Jump to search
(Add new RK3399 GPU overclocking info)
 
(81 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{warning|1= This might damage your equipment or result in a unstable system, so do this at your own risk!}}
{{warning|1= There is the possibility of damaging your equipment by overclocking. Do so at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}


Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power. You can also downclock however.
Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware).


= Preparation =
== A64-based devices ==
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.


Then after that just setup the variables for make.
{{note|These instructions are targeting the PinePhone to simplify the explanation, however they can be used to also overclock other devices such as the Pinetab if you modify the proper DTB files.}}


In the future there will likely be a driver to adjust clockspeeds from userspace without the need to recompile.
=== Editing the PinePhone DTS ===


= A64-based boards =
In order to overclock the PinePhone you will have to first convert the DTB file in <code>/boot/dtbs/allwinner/</code> to a DTS file. You will see <code>sun50i-a64-pinephone-1.2.dtb</code>, and also two other files with different PinePhone mainboard revisions (1.1 and 1.0). You will want to select the correct file for your PinePhone (Only choose 1.1 if you have a Braveheart, As all other consumer PinePhones use the 1.2 DTS).
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.


Look for
Once you've found the file, you can run the following command to convert the DTB to DTS:


  <nowiki>
  dtc -I dtb -O dts /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
    <GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
    <GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
    <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
    <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
    <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
    <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
  "gpmmu",
  "pp0",
  "ppmmu0",
  "pp1",
  "ppmmu1",
  "pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;


assigned-clocks = <&ccu CLK_GPU>;
Finally, modify the newly converted .dts file and change the clockspeeds you wish to modify. You can simply use a text editor to do so.
assigned-clock-rates = <432000000>;
};
</nowiki>


The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.
To convert back to DTB:


Save the dtsi file, and recompile the DTB.
dtc -I dts -O dtb /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb


The GPU appears to run stable overclocked to 560 Mhz, however more testing with a wider group of devices is needed.
Afterwards you can simply reboot and check with <code>sudo cat /sys/kernel/debug/clk/clk_summary</code> to see if the changes have correctly applied.


{{note|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}
{{note|In the future it is possible that someone may make a driver to adjust clockspeeds of the A64 from userspace (using a config file) without the need to recompile. However, currently the only way to overclock is to either compile your own kernel, or modify just the DTB (instructions above).}}


== CPU ==
=== GPU ===


Stock speed: 1.152GHz CPU
Open <code>/boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts</code> (You will have to find the source of the kernel used by your distribution. There is the Pine64 kernel, and Megi's) in a text editor following these instructions: https://wiki.pine64.org/wiki/Overclocking#Edit_Pinephone_DTS


== DRAM ==
Look for <code>mali: gpu@1c4000 {</code> and within that block search for <code>assigned-clock-rates = <432000000>;</code>


{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM.}}
The <code>assigned-clock-rates</code> line should be set to <code>432000000</code>, this means that the GPU is clocked at 432MHz by default. So if you want 500MHz, set the value to <code>500000000</code>.
{{info|1=Set your DRAM to a multiple of 24)


When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory.
Save the DTS file, and recompile the DTB. In order to check if the overclock was successfully applied you can run: <code>sudo cat /sys/kernel/debug/clk/clk_summary</code>.


The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however. Around 600 MHz (PC-1200) should work fine. (Some people have reported instability at lower clockspeeds, however it's not clear if the overclock was at fault)
{{note|The file may be slightly different and you may need to enter the values as hexadecimals}}
{{hint|The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed.}}
{{hint|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}


Arch Linux Arm uses a default clockspeed of 624MHz, with uboot builds availible to easily switch out for a lower DRAM clockspeed.
=== CPU ===


= Rockchip RK3399 based boards =
The stock speed of the A64 is 1.152 GHz. The A64 can be overclocked significantly, it is highly advisable not to do this unless you can also drop the voltage at the same time.
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>


More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
If the CPU is undervolted and overclocked at the same time, it is possible to reach similar thermals and power consumption to the stock configuration but with better performance.
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.


Specific to the Pinebook Pro DTS in tsys' kernels is an extra clock speed entry for the big cores in <code>arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts</code><br>
{| class=wikitable
It overrides the <code>opp08</code> entry for the big core cluster with one that runs 2GHz at 1.3V.<br>
|+ Power consumption at different voltages and frequencies
It is up to you how to deal with this, either by just skipping opp08 in the main dtsi to keep using that entry or by removing that entry from the Pinebook Pro dts and adding your own to the regular dtsi.
! Configuration
! Frequency
! Voltage
! Power (Screen 50%)
|-
! Stock
| 1.152GHz || 1.30v || ~4.35w
|-
! Stock + Undervolt
| 1.152GHz || 1.18v || ~3.65w
|-
! Overclock + Undervolt
| 1.344Ghz || 1.28v || ~4.60w
|}
The table above contains measurements created in postmarketOS (SWMO/SXMO - postmarketOS 21.12 SP1) with the screen on (set to 50% brightness) under a threaded load.


==GPU==
{| class=wikitable
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>
|+ AXP803 PMIC voltage steps on DCDC2.
! Voltage range
! Step size
|-
! 0.50V-1.20V
| 10mV
|-
! 1.22V-1.30V
| 20mV
|-
|}
The table above shows the valid voltages provided by the AXP803 PMIC on DCDC2 (used to power the cores). For example, setting the voltage to 0.60V is valid, but setting it to 1.23V is not. When overclocking, ensure that you only use valid voltages at each operation point (otherwise it will simply be dropped and ignored). You can use (after installing) cpupower to display all valid frequencies after boot.


The highest safe voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.
{{note|The user ''somefoo'' was able to undervolt the PinePhone at each frequency operation point by at least -100mv. The A64 set to 1.152Ghz runs at 1.18v instead of the standard 1.3v, dropping the power usage by ~0.7w under full single threaded load! The silicon lottery will dictate how well you can undervolt.}}
{{hint|The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as ''stress-ng'') to ensure stability.}}


TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable.
=== DRAM ===


The stock speed for the GPU is 800Mhz
{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM. 648MHz is likely the upper limit.}}
{{hint|Make sure to set your DRAM to a multiple of 24.}}
{{hint|The current frequency your DRAM is running at can be found using this command: <code>cat /proc/device-tree/memory/ram_freq</code>}}


==CPU==
When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.
 
Around 600 MHz (PC-1200) should work fine, however some people have reported instability at lower clockspeeds. Arch Linux Arm uses a default clockspeed of 552MHz, with U-Boot builds available to easily switch out for a higher (624) or lower (492) DRAM clockspeed.
 
It is possible that by reverse engineering the DRAM driver from Allwinner that auto tuning can be accomplished to get the best performance.
 
Setting the DRAM clock is accomplished by modifying pinephone_defconfig in U-Boot (https://gitlab.com/pine64-org/u-boot/-/blob/crust/configs/pinephone_defconfig)
 
You can find simple instructions on doing so here: [[U-Boot]]
 
=== VPU ===
 
In order to allocate more VRAM for the GPU you can add <code>cma=256</code> to your kernel (or use kconfig with CONFIG_CMA_SIZE_MBYTES=256) cmdline in boot.scr which you will have to compile using mkimage. By default the kernel allocates only 64MB, and the maximum value is 256MB.
 
In order to compile boot.scr you can run <code>mkimage -C none -A arm64 -T script -d boot.cmd boot.scr</code>
 
{{note|You may not have a boot.cmd file in your boot directory and instead you may instead have a boot.txt}}
 
=== Cedrus ===
 
Overclocking cedrus is achieved by modifying the kernel source code: https://elixir.bootlin.com/linux/latest/source/drivers/staging/media/sunxi/cedrus/cedrus.c#L507
 
{{note|User ''33yn2'' is not particularly sure if this makes any difference, or if it might in fact have a negative impact. Probably not worth messing with.}}
 
== RK3399-based devices ==
The RK3399 clocks are found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi]
 
More optimised voltages and clocks can be found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi]
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many Chromebooks but have worked fine in all recorded cases on regular RK3399 SoCs in other devices.
 
===GPU===
Available clock speeds for the GPU can be found and modified in <code>gpu_opp_table</code>.
 
The highest recommended voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.
 
The GPU does not have its own PLL like the CPU clusters and memory so adding new clock speed options depends on the speed of other PLLs in the system, however depending on the device these often can't be changed without breaking some functionality.
 
Without changing the PLLs the next step up from 800MHz is 1GHz, which is not known to be stable on any units.
 
In general overclocking the GPU in the RK3399 seems to be a bad idea, it usually ends up reducing performance or crashing the system entirely, possibly due to some kind of silent errors. Generally even with higher voltages there are no meaningful performance gains past 800MHz.
 
===CPU===
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.


These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.
These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.


There is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.
The maximum limit is 1.8GHz on the little cores and 2.2GHz on the big cores.
 
The highest recommended voltage for the little cores is 1.2V and for the big cores is 1.25V.
 
Segfault has found that the RK3399 in his Pinebook Pro can reach 1.7GHz on the little cores and 2.08GHz on the big ones.
 
The stock speed for the little cores is 1.4GHz and on the big cores it is 1.8GHz, the OP1 speeds default to 1.5GHz and 2.0GHz instead.
 
== ROCK64 ==
 
DTB is in <code>/boot/dtbs/rockchip/rk3328-rock64.dtb</code>. CPU clock rates are inside <code>opp_table0</code> as hexadecimal numbers in the <code>opp-hz</code> field.
 
Check the achieved clock speed with <code>sudo cat /sys/kernel/debug/clk/clk_summary | grep armclk</code>.


The highest safe voltage for the little cores is 1.2V and for the big cores is 1.25V.
Thanks to [https://github.com/ayufan-rock64 Ayufan]'s work (with their [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/overclocking.md overclocking recipe]), we know we can add a <strong>1.392GHz</strong> operating point, and a <strong>1.512GHz</strong> operating point (you should ensure you have a large heatsink for this last one). You can do so by adding the following in the <code>opp_table0</code> object, after the <code>opp-1296000000</code> operating point:


TuxThePenguin has found that the little cores on his RK3399 can run at 1.6GHz, and 2.08GHz on the big cores.
opp-1392000000 {
        opp-hz = <0x00 0x52f83c00>;
        opp-microvolt = <0x149970>;
        clock-latency-ns = <0x9c40>;
};
opp-1512000000 {
        opp-hz = <0x00 0x5a1f4a00>;
        opp-microvolt = <0x162010>;
        clock-latency-ns = <0x9c40>;
};


==DRAM==
GPU needs investigating, but current mainline device tree does not try to clock up the GPU at all.
TODO




= Rockchip RK3328 based boards =
[[Category:SOPINE]] [[Category:PINE A64]] [[Category:PINE H64]] [[Category:PINE A64-LTS]] [[Category:Pinebook]] [[Category:PinePhone]] [[Category:PineTab]] [[Category:ROCK64]] [[Category:Pinebook Pro]] [[Category:ROCKPro64]] [[Category:Allwinner A64]] [[Category:Allwinner H6]] [[Category:Rockchip RK3399]]
TODO

Latest revision as of 08:37, 29 November 2023

Warning: There is the possibility of damaging your equipment by overclocking. Do so at your own risk!
This page is incomplete, you're welcome to improve it.
All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it here.

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware).

A64-based devices

These instructions are targeting the PinePhone to simplify the explanation, however they can be used to also overclock other devices such as the Pinetab if you modify the proper DTB files.

Editing the PinePhone DTS

In order to overclock the PinePhone you will have to first convert the DTB file in /boot/dtbs/allwinner/ to a DTS file. You will see sun50i-a64-pinephone-1.2.dtb, and also two other files with different PinePhone mainboard revisions (1.1 and 1.0). You will want to select the correct file for your PinePhone (Only choose 1.1 if you have a Braveheart, As all other consumer PinePhones use the 1.2 DTS).

Once you've found the file, you can run the following command to convert the DTB to DTS:

dtc -I dtb -O dts /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts

Finally, modify the newly converted .dts file and change the clockspeeds you wish to modify. You can simply use a text editor to do so.

To convert back to DTB:

dtc -I dts -O dtb /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb

Afterwards you can simply reboot and check with sudo cat /sys/kernel/debug/clk/clk_summary to see if the changes have correctly applied.

In the future it is possible that someone may make a driver to adjust clockspeeds of the A64 from userspace (using a config file) without the need to recompile. However, currently the only way to overclock is to either compile your own kernel, or modify just the DTB (instructions above).

GPU

Open /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts (You will have to find the source of the kernel used by your distribution. There is the Pine64 kernel, and Megi's) in a text editor following these instructions: https://wiki.pine64.org/wiki/Overclocking#Edit_Pinephone_DTS

Look for mali: gpu@1c4000 { and within that block search for assigned-clock-rates = <432000000>;

The assigned-clock-rates line should be set to 432000000, this means that the GPU is clocked at 432MHz by default. So if you want 500MHz, set the value to 500000000.

Save the DTS file, and recompile the DTB. In order to check if the overclock was successfully applied you can run: sudo cat /sys/kernel/debug/clk/clk_summary.

The file may be slightly different and you may need to enter the values as hexadecimals
The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed.
Remember to run a benchmark tool (such as glmark2-es2) to help check stability.

CPU

The stock speed of the A64 is 1.152 GHz. The A64 can be overclocked significantly, it is highly advisable not to do this unless you can also drop the voltage at the same time.

If the CPU is undervolted and overclocked at the same time, it is possible to reach similar thermals and power consumption to the stock configuration but with better performance.

Power consumption at different voltages and frequencies
Configuration Frequency Voltage Power (Screen 50%)
Stock 1.152GHz 1.30v ~4.35w
Stock + Undervolt 1.152GHz 1.18v ~3.65w
Overclock + Undervolt 1.344Ghz 1.28v ~4.60w

The table above contains measurements created in postmarketOS (SWMO/SXMO - postmarketOS 21.12 SP1) with the screen on (set to 50% brightness) under a threaded load.

AXP803 PMIC voltage steps on DCDC2.
Voltage range Step size
0.50V-1.20V 10mV
1.22V-1.30V 20mV

The table above shows the valid voltages provided by the AXP803 PMIC on DCDC2 (used to power the cores). For example, setting the voltage to 0.60V is valid, but setting it to 1.23V is not. When overclocking, ensure that you only use valid voltages at each operation point (otherwise it will simply be dropped and ignored). You can use (after installing) cpupower to display all valid frequencies after boot.

The user somefoo was able to undervolt the PinePhone at each frequency operation point by at least -100mv. The A64 set to 1.152Ghz runs at 1.18v instead of the standard 1.3v, dropping the power usage by ~0.7w under full single threaded load! The silicon lottery will dictate how well you can undervolt.
The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as stress-ng) to ensure stability.

DRAM

Warning: It is not recommended to exceed 667 MHz clockspeed on the DRAM. 648MHz is likely the upper limit.
Make sure to set your DRAM to a multiple of 24.
The current frequency your DRAM is running at can be found using this command: cat /proc/device-tree/memory/ram_freq

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.

Around 600 MHz (PC-1200) should work fine, however some people have reported instability at lower clockspeeds. Arch Linux Arm uses a default clockspeed of 552MHz, with U-Boot builds available to easily switch out for a higher (624) or lower (492) DRAM clockspeed.

It is possible that by reverse engineering the DRAM driver from Allwinner that auto tuning can be accomplished to get the best performance.

Setting the DRAM clock is accomplished by modifying pinephone_defconfig in U-Boot (https://gitlab.com/pine64-org/u-boot/-/blob/crust/configs/pinephone_defconfig)

You can find simple instructions on doing so here: U-Boot

VPU

In order to allocate more VRAM for the GPU you can add cma=256 to your kernel (or use kconfig with CONFIG_CMA_SIZE_MBYTES=256) cmdline in boot.scr which you will have to compile using mkimage. By default the kernel allocates only 64MB, and the maximum value is 256MB.

In order to compile boot.scr you can run mkimage -C none -A arm64 -T script -d boot.cmd boot.scr

You may not have a boot.cmd file in your boot directory and instead you may instead have a boot.txt

Cedrus

Overclocking cedrus is achieved by modifying the kernel source code: https://elixir.bootlin.com/linux/latest/source/drivers/staging/media/sunxi/cedrus/cedrus.c#L507

User 33yn2 is not particularly sure if this makes any difference, or if it might in fact have a negative impact. Probably not worth messing with.

RK3399-based devices

The RK3399 clocks are found in arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi

More optimised voltages and clocks can be found in arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many Chromebooks but have worked fine in all recorded cases on regular RK3399 SoCs in other devices.

GPU

Available clock speeds for the GPU can be found and modified in gpu_opp_table.

The highest recommended voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

The GPU does not have its own PLL like the CPU clusters and memory so adding new clock speed options depends on the speed of other PLLs in the system, however depending on the device these often can't be changed without breaking some functionality.

Without changing the PLLs the next step up from 800MHz is 1GHz, which is not known to be stable on any units.

In general overclocking the GPU in the RK3399 seems to be a bad idea, it usually ends up reducing performance or crashing the system entirely, possibly due to some kind of silent errors. Generally even with higher voltages there are no meaningful performance gains past 800MHz.

CPU

A set of available clock speeds that can be added to the CPU clusters can be found in drivers/clk/rockchip/clk-rk3399.c under rk3399_cpuclkl_rates for the little cores and rk3399_cpuclkb_rates for the big cores.

These clock speeds can be added to cluster0_opp for the small cores and cluster1_opp for the big cores respectively.

The maximum limit is 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest recommended voltage for the little cores is 1.2V and for the big cores is 1.25V.

Segfault has found that the RK3399 in his Pinebook Pro can reach 1.7GHz on the little cores and 2.08GHz on the big ones.

The stock speed for the little cores is 1.4GHz and on the big cores it is 1.8GHz, the OP1 speeds default to 1.5GHz and 2.0GHz instead.

ROCK64

DTB is in /boot/dtbs/rockchip/rk3328-rock64.dtb. CPU clock rates are inside opp_table0 as hexadecimal numbers in the opp-hz field.

Check the achieved clock speed with sudo cat /sys/kernel/debug/clk/clk_summary | grep armclk.

Thanks to Ayufan's work (with their overclocking recipe), we know we can add a 1.392GHz operating point, and a 1.512GHz operating point (you should ensure you have a large heatsink for this last one). You can do so by adding the following in the opp_table0 object, after the opp-1296000000 operating point:

opp-1392000000 {
        opp-hz = <0x00 0x52f83c00>;
        opp-microvolt = <0x149970>;
        clock-latency-ns = <0x9c40>;
};

opp-1512000000 {
        opp-hz = <0x00 0x5a1f4a00>;
        opp-microvolt = <0x162010>;
        clock-latency-ns = <0x9c40>;
};

GPU needs investigating, but current mainline device tree does not try to clock up the GPU at all.