dc_capture_r...ftware_state(9)

✨ dc_capture_register_software_state(9) — bestie edition ✨

okay so this is from the Kernel API Manual, page dc_capture_r...ftware_state(9) (yes the title got truncated, she's mysterious like that 💅). Buckle up, we're grabbing a whole snapshot of software state.

---

🌸 NAME 🌸

dc_capture_register_software_state — capture software state so we can program registers, no cap.

---

🦋 SYNOPSIS 🦋

bool dc_capture_register_software_state (struct dc *dc , struct
       dc_register_software_state *state );

---

🎀 ARGUMENTS 🎀

• dc — the DC context, and it's holding the current display configuration. main character energy fr.
• state — a pointer to the struct dc_register_software_state structure that we're gonna populate. she starts empty, she leaves iconic ✨

---

💖 DESCRIPTION 💖

So what this does is extract literally all the software state variables that get used to program hardware register fields across the display driver pipeline. It's giving "complete snapshot of the software config that drives hardware register programming." Obsessed.

The function goes on a little tour through the DC context and pulls values from:

• Stream configurations (timing, format, DSC settings) 🌈
• Plane states (surface format, rotation, scaling, cursor) 🖱️
• Pipe contexts (resource allocation, blending, viewport) 🧚
• Clock manager (display clocks, DPP clocks, pixel clocks) ⏰
• Resource context (DET buffer allocation, ODM configuration) 🫶

And why do we care?? Because this is essential for underflow debugging 😭 — it captures the exact software state that determines how registers get programmed. That means you can actually analyze whether the underflow is caused by incorrect register programming or by timing issues. iykyk, that's the whole vibe check.

---

👑 RETURN 👑

• true — state was successfully captured, slay 💅
• false — error, we don't talk about it 🙈

---

🍓 SEE ALSO 🍓

Kernel file ./drivers/gpu/drm/amd/display/dc/dc.h plus all these besties:

• MAX_SURFACES(9)
• MAX_PLANES(9)
• color-management-caps(9)
• struct rom_curve_caps(9)
• struct dpp_color_caps(9)
• struct mpc_color_caps(9)
• struct dc_color_caps(9)
• enum pipe_split_policy(9)
• dc_check_state_update(9)
• dc_update_state(9)
• dc_update_state_init(9)
• dc_update_state_prepare(9)
• dc_update_state_execute(9)
• dc_update_state_cleanup(9)
• struct dc_probe_latencies(9)
• struct dc_probe_status(9)
• enum dc_get_status_type(9)
• struct dc_get_status_options(9)
• struct dc_state_status(9)
• dc_state_get_status(9)
• struct dc_validation_stream(9)
• struct dc_validation_set(9)
• dc_get_underflow_debug_data_for_otg(9)
• dc_get_qos_info(9)
• dc_override_memory_bandwidth_request(9)

---

lowkey the whole point: grab the state, debug the underflow, don't touch anything you didn't read about here 💀

Sign-off time 🫶 — this page lives over in ./drivers/gpu/drm/amd/display/dc, stamped October 2026, and the page name is dc_capture_r...ftware_state(9) in case you forgot already. bye bestie, go capture some state ✨🎀