summaryrefslogtreecommitdiffstats
path: root/drivers/rapidio
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ti.com>2012-10-22 16:58:36 +0300
committerTomi Valkeinen <tomi.valkeinen@ti.com>2012-11-05 11:17:39 +0200
commita5b8399fb6866be6ca065d8ab5eb7d8775d0ad26 (patch)
tree4d60b4580edfb1744a1832ff06c93e6d9b9770eb /drivers/rapidio
parent13a1a2b2a68d00d8d81417606571e004e10f6d91 (diff)
downloadblackbird-op-linux-a5b8399fb6866be6ca065d8ab5eb7d8775d0ad26.tar.gz
blackbird-op-linux-a5b8399fb6866be6ca065d8ab5eb7d8775d0ad26.zip
OMAPDSS: hide dss_select_dispc_clk_source()
dss.c currently exposes functions to configure the dispc source clock and lcd source clock. There are configured separately from the output drivers. However, there is no safe way for the output drivers to handle dispc clock, as it's shared between the outputs. Thus, if, say, the DSI driver sets up DSI PLL and configures both the dispc and lcd clock sources to that DSI PLL, the resulting dispc clock could be too low for, say, HDMI. Thus the output drivers should really only be concerned about the lcd clock, which is what the output drivers actually use. There's lot to do to clean up the dss clock handling, but this patch takes one step forward and removes the use of dss_select_dispc_clk_source() from the output drivers. After this patch, the output drivers only configure the lcd source clock. On omap4+ the dispc src clock is never changed from the default PRCM source. On omap3, where the dispc and lcd clocks are actually the same, setting the lcd clock source sets the dispc clock source. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'drivers/rapidio')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud