drm_dp_dsc_..._slice_count(9)

📦 version 7.3.1, in nixpkgs unstable

✨ drm_dp_dsc_sink_max_slice_count — Kernel API Manual 🎀

okay bestie, welcome to the drm_dp_dsc_sink_max_slice_count(9) page 💅 (that's the manual name right there, in case the header didn't already spoil it). This is a kernel API page about Display Stream Compression slice counts — yes it's niche, yes it's iconic, let's go 🦋

🌸 NAME 🌸

drm_dp_dsc_sink_max_slice_count — get the max slice count supported by the DSC sink. that's the whole vibe lowkey 💖

🦋 SYNOPSIS 🦋

u8 drm_dp_dsc_sink_max_slice_count (const u8
dsc_dpcd[DP_DSC_RECEIVER_CAP_SIZE] , bool is_edp );

literally just returns a u8, no cap 🙈

🎀 ARGUMENTS 🎀

  • dsc_dpcd — the DSC capabilities, straight out of DPCD 💫
  • is_edp — true if it's eDP, false for DP. choose wisely bestie, no take-backs 🫶

💜 DESCRIPTION 💜

so the way this works: it reads the slice capabilities DPCD register from the DSC sink and gets the maximum slice count supported. that's it, that's the function ✨

then, the driver uses it to populate the DSC parameters in the struct drm_dsc_config — so it goes DPCD register → struct drm_dsc_config, slay 🧚

after that the driver creates an infoframe using these parameters to populate struct drm_dsc_pps_infoframe. and those get sent to the sink using the DSC infoframe via the helper function drm_dsc_pps_infoframe_pack. cute little pipeline, honestly obsessed 👑

🔥 RETURN 🔥

the maximum slice count supported by the DSC sink — or 0 if it's invalid 💀 (yes, 0 is the "nah" signal here)

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/display/drm_dp_helper.c — here's the entire fandom, no gatekeeping 🌸

real talk: this is a lot of cross-references, and if you need the whole crew, they're all listed above — nothing skipped, nothing merged, no cap 💯

and that's the page bestie 🫶 it lives in ./drivers/gpu/drm/display and it's dated October 2026 — so yeah, future energy, main character energy, drm_dp_dsc_..._slice_count(9) energy. periodt 💅⭐

📦 where this page comes from