ENUM DRM_LVDS_DUAL_LINK_PIXELS(9)

💖 NAME 💖

enum drm_lvds_dual_link_pixels — literally tells you the pixel order of an LVDS dual-link connection, bestie ✨

So this is a page from the Kernel API Manual, and it's all about which port spits out which pixels. Lowkey iconic that something this specific gets its own enum, ngl 💅

✨ SYNOPSIS ✨

enum drm_lvds_dual_link_pixels {
    DRM_LVDS_DUAL_LINK_EVEN_ODD_PIXELS ,
    DRM_LVDS_DUAL_LINK_ODD_EVEN_PIXELS

};

Two constants, one vibe check: which port does the even pixels and which one does the odd ones 🦋 Keep the code exactly like that, commas and all — we do not touch the source, periodt.

🎀 Constants 🎀

• DRM_LVDS_DUAL_LINK_EVEN_ODD_PIXELS — the even pixels are expected to come from the first port, and the odd pixels are expected to come from the second port. Even → first, odd → second, slay 💖
• DRM_LVDS_DUAL_LINK_ODD_EVEN_PIXELS — the odd pixels are expected to come from the first port, and the even pixels are expected to come from the second port. Odd → first, even → second, the flip side of the coin 🔥

Notice the wording is "are expected to be generated from" — that's the whole story on this page, no extra lore, no cap 🙈

🦋 SEE ALSO 🦋

• Kernel file ./include/drm/drm_of.h 👑 — go read it if you want the actual context, iykyk

And that's the whole page, bestie 🫶 This one came from ./include/drm, dated October 2026, and the manual page title is enum drm_lvd..._link_pixels(9) — cute, tiny, and fully about pixel parity 🌸💜