summaryrefslogtreecommitdiffstats
path: root/include/video
diff options
context:
space:
mode:
authorArchit Taneja <archit@ti.com>2012-08-13 22:12:24 +0530
committerArchit Taneja <archit@ti.com>2012-08-16 18:02:11 +0530
commit6b84937577486a79cbc2196573ff7387a9f75cb0 (patch)
tree154a2f85e5edcc8b384f338d10f437aa59e7d856 /include/video
parentdca2b1522ccab28d03fb79f6e70e70ea78033d52 (diff)
downloadtalos-obmc-linux-6b84937577486a79cbc2196573ff7387a9f75cb0.tar.gz
talos-obmc-linux-6b84937577486a79cbc2196573ff7387a9f75cb0.zip
OMAPDSS: DSI: Rename dsi_videomode_data to dsi_videomode_timings
The struct omap_dss_dsi_videomode_data holds fields which need to be configured for DSI to operate in video mode. Rename the struct to dsi_videomode_timings. One reason to do this is because most of the fields in the struct are timings related. The other reason is to create a generic op for output specific timings. This generic op can be considered as a way to set custom or private timings for the output. In the case of OMAP, DSI and RFBI require some more timings apart from the relgular DISPC timings. The structs omap_dss_videomode_timings and rfbi_timings can be considered as these output specific timings respectively. Signed-off-by: Archit Taneja <archit@ti.com>
Diffstat (limited to 'include/video')
-rw-r--r--include/video/omapdss.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/video/omapdss.h b/include/video/omapdss.h
index ef14ac552023..363235cc642f 100644
--- a/include/video/omapdss.h
+++ b/include/video/omapdss.h
@@ -243,7 +243,7 @@ void rfbi_bus_unlock(void);
/* DSI */
-struct omap_dss_dsi_videomode_data {
+struct omap_dss_dsi_videomode_timings {
/* DSI video mode blanking data */
/* Unit: byte clock cycles */
u16 hsa;
@@ -564,7 +564,7 @@ struct omap_dss_device {
enum omap_dss_dsi_pixel_format dsi_pix_fmt;
enum omap_dss_dsi_mode dsi_mode;
- struct omap_dss_dsi_videomode_data dsi_vm_data;
+ struct omap_dss_dsi_videomode_timings dsi_vm_timings;
} panel;
struct {
OpenPOWER on IntegriCloud