Skip to content

arm64: dts: rockchip: rk3576: remove empty rockchip,supported-hw from OPP tables#484

Open
mingzhangqun wants to merge 1 commit into
armbian:rk-6.1-rkr5.1from
Seeed-Studio:fix/rk3576-opp-supported-hw
Open

arm64: dts: rockchip: rk3576: remove empty rockchip,supported-hw from OPP tables#484
mingzhangqun wants to merge 1 commit into
armbian:rk-6.1-rkr5.1from
Seeed-Studio:fix/rk3576-opp-supported-hw

Conversation

@mingzhangqun
Copy link
Copy Markdown

Summary

  • Remove empty rockchip,supported-hw; property from 7 OPP tables in rk3576.dtsi (cluster0, cluster1, bus_a72, dmc, npu, gpu, vop)
  • The bare property with no value makes the OPP framework require opp-supported-hw on every OPP entry, but only opp-j-m-* entries have it. This causes all generic OPP entries to be rejected, resulting in GPU stuck at ~100 MHz without devfreq

Test plan

  • Verify GPU devfreq scales properly on rk3576 (non-J/M variant)
  • Check CPU frequency scaling works on cluster0/cluster1
  • Verify no regression on J/M variants that use opp-supported-hw entries

… OPP tables

The bare "rockchip,supported-hw;" property with no value makes the OPP
framework require opp-supported-hw on every OPP entry, but only opp-j-m-*
entries have it. This causes all generic OPP entries to be rejected,
resulting in GPU stuck at a fixed ~100 MHz without devfreq.

Remove the empty property so standard opp-* entries are always available
for non-J/M chips.

Affects: cluster0, cluster1, bus_a72, dmc, npu, gpu, vop OPP tables.

Signed-off-by: mingzq <north_sea@qq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants