summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>2016-11-18 15:55:48 +0100
committerLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>2017-04-04 16:03:30 +0200
commit5ec1a96010aa7aff19adba92a8163ef8f8c5c1ad (patch)
tree9eec846e111cf5cfd8f59f5f9753187af6bf9d6e
parentdevicetree/bindings: display: Add bindings for two Mitsubishi panels (diff)
downloadlinux-5ec1a96010aa7aff19adba92a8163ef8f8c5c1ad.tar.xz
linux-5ec1a96010aa7aff19adba92a8163ef8f8c5c1ad.zip
drm: Add data transmission order bus flag
The flags indicate whether data is transmitted LSB to MSB or MSB to LSB on the bus. The exact meaning is bus-type dependent. For instance, for LVDS buses the flags indicate whether the seven data bits transmitted in a clock pulse are sent in normal order (MSB to LSB, slots 0 to 6) or reverse order (LSB to MSB, slots 6 to 0). Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Reviewed-by: Thierry Reding <treding@nvidia.com>
-rw-r--r--include/drm/drm_connector.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
index 941f57f311aa..8250062eb8a5 100644
--- a/include/drm/drm_connector.h
+++ b/include/drm/drm_connector.h
@@ -224,6 +224,10 @@ struct drm_display_info {
#define DRM_BUS_FLAG_PIXDATA_POSEDGE (1<<2)
/* drive data on neg. edge */
#define DRM_BUS_FLAG_PIXDATA_NEGEDGE (1<<3)
+/* data is transmitted MSB to LSB on the bus */
+#define DRM_BUS_FLAG_DATA_MSB_TO_LSB (1<<4)
+/* data is transmitted LSB to MSB on the bus */
+#define DRM_BUS_FLAG_DATA_LSB_TO_MSB (1<<5)
/**
* @bus_flags: Additional information (like pixel signal polarity) for