dcn60_updat..._with_action(9)

💅 NAME

dcn60_update_bandwidth_clocks_state_with_action — okay so bestie, this is the one that actually applies all your pending clock and p-state changes to the clk_mgr state, and it does it based on the action struct. Like, it's the moment everything gets committed. Main character energy fr fr ✨

Oh and hey — this whole page lives in the Kernel API Manual, so jot that down 🎀

✨ SYNOPSIS ✨

void dcn60_update_bandwidth_clocks_state_with_action (struct clk_mgr
*clk_mgr_base , struct dcn60_bandwidth_clocks_update_action *action ,
struct dc_clocks *new_clocks );

It returns void, ngl. Nothing comes back out — it just does the thing 💅

🫶 ARGUMENTS 🫶

• clk_mgr_base — the clock manager state you're updating, aka the glow-up target 💖
• action — the action struct, and no cap, this one has to be populated by dcn60_make_bandwidth_clocks_update_action first or you're just out here with an empty vibe
• new_clocks — the new clock values, which get copied straight into the clk_mgr state 🦋

👀 SEE ALSO 👀

Kernel file, right here, screenshot it:

./drivers/gpu/drm/amd/display/dc/clk_mgr/dcn60/dcn60_clk_mgr.c

And the whole friend group:

• dcn60_populate_dc_mode_limit(9)
• dcn60_populate_clk_table(9)
• dcn60_make_bandwidth_clocks_update_action(9)
• dcn60_build_bandwidth_clocks_block_sequence_with_action(9)
• dcn60_build_update_bandwidth_clocks_sequence(9)

Okay that's the whole page, you ate that 🍓 This lil icon was served up fresh from ./drivers/gpu/drm/amd/display/... and it's stamped October 2026 — so basically it's from the future, obsessed 💜✨