drm_of_lvds..._pixel_order(9)
πΈ drm_of_lvds..._pixel_order(9) πΈ
okay bestie, welcome to the Kernel API Manual π this one's about drm_of_lvds_get_dual_link_pixel_order and honestly? it's giving "matchmaker for pixels" energy and i'm obsessed.
β¨ NAME β¨
drm_of_lvds_get_dual_link_pixel_order β get the LVDS dual-link source pixel order, no cap π
β¨ SYNOPSIS β¨
int drm_of_lvds_get_dual_link_pixel_order (const struct device_node
*port1 , const struct device_node *port2 );
β¨ ARGUMENTS β¨
port1β the first DT port node of the Dual-link LVDS source, bestie π«Άport2β the second DT port node of the Dual-link LVDS source, its literal partner in crime π
β¨ DESCRIPTION β¨
so. an LVDS dual-link connection is made of two links, right? and the way it works is: even pixels transit on one link, and odd pixels transit on the other link. that's just the vibe π
this function returns, for two ports of an LVDS dual-link source, which port shall transmit the even and odd pixels, based on the requirements of the connected sink. it's literally doing a vibe check on behalf of the sink π
the pixel order is determined from the dual-lvds-even-pixels and dual-lvds-odd-pixels properties in the sink's DT port nodes. if those properties are not present, or if their usage is not valid, this function returns -EINVAL π
if either port is not connected, this function returns -EPIPE. not me crying in pipe error π
port1 and port2 are typically DT sibling nodes, but may have different parents when, for instance, two separate LVDS encoders carry the even and odd pixels. found family fr fr π§
β¨ RETURN β¨
DRM_LVDS_DUAL_LINK_EVEN_ODD_PIXELSβport1carries even pixels andport2carries odd pixels β¨DRM_LVDS_DUAL_LINK_ODD_EVEN_PIXELSβport1carries odd pixels andport2carries even pixels π₯-EINVALβport1andport2are not connected to a dual-link LVDS sink, or the sink configuration is invalid π-EPIPEβ whenport1orport2are not connected π
β¨ SEE ALSO β¨
go check out the Kernel file ./drivers/gpu/drm/drm_of.c overview(9) for the whole lore, plus these iconic siblings π
drm_of_crtc_port_mask(9)drm_of_find_possible_crtcs(9)drm_of_component_match_add(9)drm_of_component_probe(9)drm_of_get_panel_orientation(9)drm_of_find_panel_or_bridge(9)drm_of_lvds_get_dual_link_pixel_order_sink(9)drm_of_lvds_get_data_mapping(9)drm_of_get_data_lanes_count(9)drm_of_get_data_lanes_count_ep(9)drm_of_get_data_lanes_count_remote(9)drm_of_get_dsi_bus(9)
π tiny heads-up bestie: if you're getting-EINVALor-EPIPEback, that's the function telling you the sink config or the connection isn't it. read the return values again, don't come for me π
and that's the whole page, periodt π this icon lives in ./drivers/gpu/drm, and the date on this masterpiece is October 2026 β screenshot it, frame it, it's iconic ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms