According this u-boot for C2 still supports overclocking.
But HK had to change the DVFS implementation within the latest u-boot, as there were some boot issues with mainline kernels not supporting kernel-arg “max_freq”, resulting in failing bootup @2GHz.
Therfore they implemented two DVFS tables, a default one with 1,5GHz, and a second one with 2GHz for kernels which can handle “max_freq” (see Commit)
So it seems that CE is only missing this Commit, to make it working again for C2.
Hopefully this can be implemented in CE
Sorry for late reply. Testversion works for me on C2.
Have seen you just transferred the linux commit to CE patch. Good practice to keep the kernel source clean…
Weird. After a deeper look, it seems all AML targets are built with “CONFIG_ARCH_MESON64_ODROIDC2=y” defined?!?
Then it’s clear that the commit will cause bootfail on all other AML boards.
Maybe in this case it’s better to transfer this Commit also to a device dependend patch.
Not sure what the additional GPIO toggle may cause on other boards…