dc_update_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dc_update_state(9) β€” the Kernel API Manual glow-up πŸŽ€

okay bestie, welcome to dc_update_state(9), fresh out of the Kernel API Manual and honestly? iconic. this is the page where you commit an absolute dc_state_update and honestly it's giving main character energy πŸ’–


✨ NAME ✨

dc_update_state β€” commit an absolute dc_state_update. that's it. that's the whole vibe. no cap 🫢


🌸 SYNOPSIS 🌸

bool dc_update_state (struct dc *dc , const struct dc_state_update
*updates );

look at her. two args. returns a bool. she's lowkey so clean for it πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dc β€” the DC structure. your whole display core situation, the main character of this function fr fr πŸ‘‘
  • updates β€” the root update object, and she's carrying everything: stream updates, plane updates, and probe updates. like a bestie holding all the snacks πŸ“βœ¨

⭐ RETURN ⭐

true on success, false on failure. that's the vibe check β€” if it comes back true we're slaying, if it comes back false... 😭 well. at least you know.


πŸ”₯ SEE ALSO πŸ”₯

okay this list is LONG but every single one of these is a real one, no skips, we don't do skips here πŸ’€

ngl the state-update pipeline is a whole friend group: dc_check_state_update(9) checks, dc_update_state_init(9) sets it up, dc_update_state_prepare(9) gets ready, dc_update_state_execute(9) does the thing, dc_update_state_cleanup(9) cleans up after β€” and dc_update_state is the one who commits. everybody plays their part, periodt πŸ’œ

kay that's the whole page bestie, go commit some state responsibly πŸ’–βœ¨

this serve was brought to you by ./drivers/gpu/drm/amd/display/dc, dated October 2026 β€” mwah, catch you on the next manpage πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from