| author | Archit Taneja <archit@ti.com> | |
| Mon, 6 May 2013 15:36:06 +0000 (17:36 +0200) | ||
| committer | Archit Taneja <archit@ti.com> | |
| Thu, 30 May 2013 23:03:37 +0000 (04:33 +0530) | ||
| commit | 508669f4b58e719659cf7b3ebe48e7ae1a0ea3ca | |
| tree | 3957e128bab1cc7ff8637cfbb04734dfb09081fa | tree | snapshot (tar.xz tar.gz zip) |
| parent | b3a26e720a6e1e3249f6dc2c9f199ae9d3a02973 | commit | diff |
omapdss: hdmi: fix deepcolor mode configuration
The hdmi driver supports deep color modes. However, there is a specific check
which doesn't allow 1080p timings or higher to be shown 36 bit deep color mode.
The more generic check would be to check if the pixel clock in a deep color mode
is less than the maximum pixel clock the TV overlay manager can support for the
given OMAP. Make this change.
Also, make sure that hdmi.dssdev is assigned by the end of probe, this param is
needed by the deepcolor sysfs attribute file.
Signed-off-by: Archit Taneja <archit@ti.com>
The hdmi driver supports deep color modes. However, there is a specific check
which doesn't allow 1080p timings or higher to be shown 36 bit deep color mode.
The more generic check would be to check if the pixel clock in a deep color mode
is less than the maximum pixel clock the TV overlay manager can support for the
given OMAP. Make this change.
Also, make sure that hdmi.dssdev is assigned by the end of probe, this param is
needed by the deepcolor sysfs attribute file.
Signed-off-by: Archit Taneja <archit@ti.com>