From PINE64
Jump to navigation Jump to search
This might damage your equipment or may result in a unstable system, so do this at your own risk!
This page is incomplete, you're welcome to improve it.
Overclocked devices may seem stable but crash occasionally and be hard to debug. A good test suite needs to be found to properly test the entire functionality of overclocked devices to properly ensure stability
Keep a backup bootable OS which is known to be stable, if an overclock fails you may not be able to boot the system without another OS
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 and better performance out of the system by running it at higher clock speeds than the factory default.


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.

A64-based boards


Open arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi in a text editor.

Look for

		mali: gpu@1c40000 {
			compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
			reg = <0x01c40000 0x10000>;
			interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
			interrupt-names = "gp",
			clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
			clock-names = "bus", "core";
			resets = <&ccu RST_BUS_GPU>;

			assigned-clocks = <&ccu CLK_GPU>;
			assigned-clock-rates = <432000000>;

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

Save the dtsi file, and recompile the DTB.

Danct12 has found on his Pinetab that 562 MHz is the limit for stable operation.
Remember to run a benchmark tool (such as glmark2-es2) to make sure that it's stable! If it's not, then lower the clock speed until you can get a stable clock speed.




It is not recommended to exceed 672 MHz clockspeed on the DRAM.

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.

Rockchip RK3399 based boards

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 RK3399s in other devices.


Any clock speeds can be added for the GPU in gpu_opp_table

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

TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable, 1GHz was tried but crashed instantly.


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.

Any of the clock speeds listed in this file can be added but no others will work, this means there is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.

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

TuxThePenguin has found that the little cores on his RK3399 would run at 1.7GHz and the big cores would run at 2.1GHz, however a crash was encountered at this frequency so speeds were stepped back to 1.6GHz on the little cores and 2.08GHz on the big cores, make sure to thoroughly check for stability!



Rockchip RK3328 based boards