drm_edid_read_ddc(9)

📦 version 7.3.1, in nixpkgs unstable

✨ drm_edid_read_ddc(9) ✨

okay bestie, welcome to the Kernel API Manual page for drm_edid_read_ddc — it's giving "I read monitors for a living" and honestly? iconic. 💅

🌸 NAME 🌸

drm_edid_read_ddc — read EDID data using the given I2C adapter. that's it, that's the whole vibe 🎀

🦋 SYNOPSIS 🦋

const struct drm_edid * drm_edid_read_ddc (struct drm_connector
*connector , struct i2c_adapter *adapter );

like yes it's two args and a return type, we love a compact signature 🔥

💖 ARGUMENTS 💖

  • connector — the connector you're working with. your main character 🫶
  • adapter — the I2C adapter to use for DDC. this is the little messenger that goes and chats with your display 💌

👑 DESCRIPTION 👑

so basically: read the EDID using the given I2C adapter. no cap, that's the core job.

BUT — plot twist — the EDID might get overridden 🫢 either by the debugfs override_edid, or by the firmware EDID (that's drm_edid_load_firmware and the drm.edid_firmware parameter). and bestie, that's the priority order, exactly like that. if either one of them is present, it straight-up bypasses the actual EDID reads. like, no real reading happens. skipped. byeee 👋

💀 real talk though: prefer initializing connector->ddc with drm_connector_init_with_ddc and using drm_edid_read instead of this function. that's the glow-up path, fr fr.

also!! the returned pointer must be freed using drm_edid_free. do not ghost your allocations, bestie, that's how leaks happen 😭

⭐ RETURN ⭐

pointer to EDID 🌈 — or NULL if the probe/read failed 🙈 (iykyk, sometimes the display just doesn't wanna talk)

🧚 SEE ALSO 🧚

the kernel file lives at ./drivers/gpu/drm/drm_edid.c — go say hi 💜

and the whole friend group:

and that's the whole page, bestie! 🌈✨ this lil masterpiece lives in ./drivers/gpu/drm, dated October 2026, and it's filed under drm_edid_read_ddc(9) — go forth and read those EDIDs responsibly 💖🎀🦋

📦 where this page comes from