drm/tegra: hdmi: Explicitly set clock rate
authorThierry Reding <treding@nvidia.com>
Wed, 18 Feb 2015 09:34:08 +0000 (10:34 +0100)
committerThierry Reding <treding@nvidia.com>
Thu, 19 Feb 2015 13:21:25 +0000 (14:21 +0100)
commitc03bf1bfd3a5448a4474f02b839f2195e3719cd9
tree5c26459346ad238abad0b20161b9f20899291449
parent45ee2dbc65cbf6910892c480e6f428be342fa733
drm/tegra: hdmi: Explicitly set clock rate

Recent changes in the clock framework have caused a behavioural change
in that clocks that have not had their rate set explicitly will now be
reset to their initial rate (or 0) when the clock is released. This is
triggered in the deferred probing path, resulting in the clock running
at a wrong frequency after the successful probe.

This can be easily fixed by setting the rate explicitly rather than by
relying on the implicit rate inherited by the parent.

Tested-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
drivers/gpu/drm/tegra/hdmi.c