STRUCT DRM_DP_PHY_TEST_PARAMS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct drm_dp_phy_test_params(9) β€” like, the Kernel API Manual edition πŸŽ€

okay bestie, buckle up, because this one lives in the Kernel API Manual and it's basically the little glow-up form your DisplayPort PHY fills out for compliance testing ✨ it's giving "backstage pass to the DPCD registers" and honestly? obsessed.


🌸 NAME 🌸

struct drm_dp_phy_test_params β€” the DP Phy Compliance parameters, periodt. πŸ’–


✨ SYNOPSIS ✨

struct drm_dp_phy_test_params {
    int link_rate;
    u8 num_lanes;
    u8 phy_pattern;
    u8 hbr2_reset[2];
    u8 custom80[10];
    bool enhanced_frame_cap;
 };

like, that's the whole vibe right there 🫢 every single field, no cap.


πŸ¦‹ Members πŸ¦‹

  • link_rate β€” the Requested Link rate that came in from DPCD 0x219 πŸ’« literally the speed they're asking for.
  • num_lanes β€” the Number of lanes requested by sing through DPCD 0x220 πŸ›£οΈ (yes that's the exact wording, don't come for me, I just report the facts).
  • phy_pattern β€” the DP Phy test pattern straight outta DPCD 0x248 🎨 the main character of this whole struct, ngl.
  • hbr2_reset β€” DP HBR2_COMPLIANCE_SCRAMBLER_RESET from DCPD 0x24A and 0x24B πŸ” a two-byte reset moment, iconic.
  • custom80 β€” DP Test_80BIT_CUSTOM_PATTERN from DPCDs 0x250 through 0x259 🌈 ten whole bytes of custom pattern, we love a DIY moment.
  • enhanced_frame_cap β€” flag for enhanced frame capability πŸ‘‘ a bool, so it's just yes/no energy.

πŸ’œ SEE ALSO πŸ’œ

go read the Kernel file ./include/drm/display/drm_dp_helper.h fr fr, plus these absolute legends:


🫢 quick vibe check: this page is sourced from ./include/drm/display and it's dated October 2026 β€” so yeah, future-flavored documentation, slay πŸ’…

k bye, go test those PHYs, you're gonna ate πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from