drm_dp_read_lttpr_phy_caps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_dp_read_lttpr_phy_caps(9) β€” Kernel API Manual πŸ’–

okay bestie, welcome to the group chat for this page from the Kernel API Manual ✨ it's giving kernel display-helper realness, and we're here to read the capabilities for one specific LTTPR PHY. no cap.

✨ NAME ✨

drm_dp_read_lttpr_phy_caps β€” read the capabilities for a given LTTPR PHY πŸ’…

🌸 SYNOPSIS 🌸

int drm_dp_read_lttpr_phy_caps (struct drm_dp_aux *aux , const u8
dpcd[DP_RECEIVER_CAP_SIZE] , enum drm_dp_phy dp_phy , u8
caps[DP_LTTPR_PHY_CAP_SIZE] );

πŸŽ€ ARGUMENTS πŸŽ€

  • aux β€” DisplayPort AUX channel. literally the AUX channel, bestie πŸ’«
  • dpcd β€” DisplayPort configuration data. the config data, periodt.
  • dp_phy β€” LTTPR PHY to read the capabilities for. this is the one we're reading about πŸ‘‘
  • caps β€” buffer to return the capability info in. it's where the capability info goes, slay 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

Read the capabilities for the given LTTPR PHY. that's the whole quest πŸ’–

It returns 0 on success or a negative error code on failure. so yes: success is 0, failure is a negative error code, and there is no in-between main-character nonsense here 😭

🌈 SEE ALSO 🌈

the whole squad of related pages, no cap:


okay that's the page, bestie πŸ’– source/version vibes: ./drivers/gpu/drm/display, dated October 2026, and the page is drm_dp_read_lttpr_phy_caps(9). bye and slay βœ¨πŸ¦‹

πŸ“¦ where this page comes from