DALSMC_MSG_U...TMQoSRequest(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Okay bestie, welcome to the DALSMC_MSG_U...TMQoSRequest(9) page from the Kernel API Manual β€” the main character here is DALSMC_MSG_UpdateUTMQoSRequest, and its whole job is: Update the active UTM QoS bandwidth/latency request. slay πŸŽ€


✨ SYNOPSIS ✨

DALSMC_MSG_UpdateUTMQoSRequest

Literally just that in the synopsis, no extra args shown β€” it’s giving minimal icon behavior πŸ’….


πŸ¦‹ DESCRIPTION πŸ¦‹

So here’s the tea, bestie: DALSMC_MSG_UpdateUTMQoSRequest passes the current display bandwidth and latency requirements to PMFW so it can select the appropriate SoC operating point (UCLK/FCLK level) from the UTM table. Highkey important: it’s called whenever the display configuration changes. πŸ”₯

The QoS requirement must take effect before PMFW sends its response. No cap β€” that ordering is serious, fr fr. ⏳

Request:

  • LatencySopIndex β€” index into the UTM SOP table that satisfies latency
  • NominalBandwidthKBps β€” required nominal (average) bandwidth in KB/s
  • UrgentBandwidthKBps β€” required urgent bandwidth in KB/s
  • LsdmaBandwidthKBps β€” required LSDMA bandwidth in KB/s

Response: (none beyond result code) β€” nothing extra comes back beyond the result code, periodt. πŸ™ˆ


🌈 SEE ALSO 🌈

The related bestie squad, iykyk:


And that’s the page, bestie 🫢 β€” footer energy: source/version is ./drivers/gpu/drm/amd/display/..., date is October 2026, and the footer page name is DALSMC_MSG_U...TMQoSRequest(9). Byeee πŸ’–βœ¨

πŸ“¦ where this page comes from