drm: bridge: Add dual_link field to the drm_bridge_timings structure
authorLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Mon, 4 Mar 2019 21:05:34 +0000 (23:05 +0200)
committerLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Fri, 7 Jun 2019 23:36:04 +0000 (02:36 +0300)
Extend the drm_bridge_timings structure with a new dual_link field to
indicate that the bridge's input bus carries data on two separate
physical links. The first use case is LVDS dual-link mode where even-
and odd-numbered pixels are transferred on separate LVDS links.

Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Tested-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
include/drm/drm_bridge.h

index d4428913a4e14981d93dc534780737d07940a4ae..aea1fcfd92a7da30cb4a5c941936241cd45c5d91 100644 (file)
@@ -265,6 +265,14 @@ struct drm_bridge_timings {
         * input signal after the clock edge.
         */
        u32 hold_time_ps;
+       /**
+        * @dual_link:
+        *
+        * True if the bus operates in dual-link mode. The exact meaning is
+        * dependent on the bus type. For LVDS buses, this indicates that even-
+        * and odd-numbered pixels are received on separate links.
+        */
+       bool dual_link;
 };
 
 /**