Hi,
Recently I find that no matter what opp tables I'm using (default and op1), the RockPro64 board always failed to add the opp table with the following error messages:
[ 2.443667] rk3399-dmc-freq ffa80000.dmc: supply center not found, using dummy regulator
[ 2.444366] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 2.444527] rk3399-dmc-freq ffa80000.dmc: Invalid operating-points in device tree.
[ 2.445037] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 2.445661] rk3399-dmc-freq: probe of ffa80000.dmc failed with error -22
I tried the default opp table (rk3399-opp.dts) and the op1, they both failed with the same messages.
Upstream kernel v5.14.2 (With one commit reverted to address the ethernet regression) and upstream v5.15-rc1 kernels both tested, no good result.
Is there some regression in rockchip related code that prevents the default/op1 opp tables from getting applied properly?
Thanks,
Qu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
On 2021/9/17 10:45, Qu Wenruo wrote:
Hi,
Recently I find that no matter what opp tables I'm using (default and op1), the RockPro64 board always failed to add the opp table with the following error messages:
[ 2.443667] rk3399-dmc-freq ffa80000.dmc: supply center not found, using dummy regulator
[ 2.444366] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 2.444527] rk3399-dmc-freq ffa80000.dmc: Invalid operating-points in device tree.
[ 2.445037] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 2.445661] rk3399-dmc-freq: probe of ffa80000.dmc failed with error -22
Sorry, false alert.
My setup of Uboot->systemd-boot->kernel is not working as expected.
The main problem here is in systemd-boot, even I have specified "devicetree" key, it's not loading the proper device tree.
And Uboot is not loading the proper device tree either, as it tries to load from "/", "/dtb" and "/dtb/current", not "/dtbs" used in the distro.
Thus I should report the problem to the systemd-boot part, as that's where I specify the device tree.
Currently I can just rename the device tree directory but I really want to have the ability to choose kernel/device-tree combination in systemd-boot.
Thanks,
Qu
I tried the default opp table (rk3399-opp.dts) and the op1, they both failed with the same messages.
Upstream kernel v5.14.2 (With one commit reverted to address the ethernet regression) and upstream v5.15-rc1 kernels both tested, no good result.
Is there some regression in rockchip related code that prevents the default/op1 opp tables from getting applied properly?
Thanks,
Qu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel