drm_dp_dual_mode_detect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_dp_dual_mode_detect πŸ’…

okay so this is a page from the Kernel API Manual, bestie β€” we're deep in kernel-land, and this little function is here to help you figure out what kind of DP dual mode adaptor you're actually holding. Slay. Let's get into it 🫢


✨ NAME ✨

drm_dp_dual_mode_detect β€” literally just: identify the DP dual mode adaptor πŸ”


🌸 SYNOPSIS 🌸

enum drm_dp_dual_mode_type drm_dp_dual_mode_detect (const struct
drm_device *dev , struct i2c_adapter *adapter );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the drm_device to use. that's your main character right there πŸ‘‘
  • adapter β€” the I2C adapter for the DDC bus. yes, the DDC bus, no cap πŸ¦‹

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does it do? It attempts to identify the type of the DP dual mode adaptor used. That's the whole vibe check πŸ’…

⚠️ but bestie, listen β€” when the answer comes back as DRM_DP_DUAL_MODE_UNKNOWN, it's not certain whether we're dealing with a native HDMI port or a type 1 DVI dual mode adaptor. like, genuinely unclear 😭 the driver is gonna have to use some other hardware/driver specific mechanism to make that distinction. not me having to figure it out myself πŸ’€

⭐ RETURN ⭐

It returns the type of the DP dual mode adaptor used ✨ that's it, that's the tea πŸ“


🌈 SEE ALSO 🌈

  • Kernel file ./drivers/gpu/drm/display/drm_dp_dual_mode_helper.c β€” the dp dual mode helpers(9), iconic behaviour honestly
  • drm_dp_dual_mode_read(9)
  • drm_dp_dual_mode_write(9)
  • drm_dp_dual_mode_max_tmds_clock(9)
  • drm_dp_dual_mode_get_tmds_output(9)
  • drm_dp_dual_mode_set_tmds_output(9)
  • drm_dp_get_dual_mode_type_name(9)
  • drm_lspcon_get_mode(9)
  • drm_lspcon_set_mode(9)

and that's a wrap, bestie πŸ§šπŸ’œ this one came straight out of ./drivers/gpu/drm/display, dated October 2026 β€” go forth and identify those adaptors, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from