ENUM DC_PROBE_TARGET_STATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay bestie, welcome to enum dc_probe_target_state(9) β€” the Kernel API Manual page for the target lifecycle state that DM wants DC to reach. it’s giving β€œfinal form” energy ✨

✨ SYNOPSIS ✨

enum dc_probe_target_state {
    DC_PROBE_NOT_MEASURING ,
    DC_PROBE_MEASURING ,
    DC_PROBE_MEASURED

};

πŸŽ€ Constants πŸŽ€

  • DC_PROBE_NOT_MEASURING β€” probe is inactive, so no valid data is available. literally nothing to read, bestie.
  • DC_PROBE_MEASURING β€” the probe runs continuously. The latest value can be read back at any time and may differ on each read. so yes, every read can be a whole new vibe.
  • DC_PROBE_MEASURED β€” the probe performed one shot. The result is latched and stays valid until DM transitions back to DC_PROBE_NOT_MEASURING. locked in, periodt.

πŸ¦‹ Description πŸ¦‹

DM sets this to describe the final state DC must reach by the end of the commit. DC performs whatever HW transition sequence is needed. that’s the assignment, and DC handles the HW transition sequence 🌸

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/amd/display/dc/dc_probe.h β€” plus these iconic besties:

  • enum dc_probe_type(9)
  • enum dc_probe_scope_type(9)
  • struct dc_probe_scope(9)
  • struct dc_probe_state(9)
  • struct dc_probe_updates(9)

xoxo from the ./drivers/gpu/drm/amd/display/dc girlies πŸ’… β€” October 2026 🫢

πŸ“¦ where this page comes from