summaryrefslogtreecommitdiffstats
path: root/include/video/sh_mobile_lcdc.h
diff options
context:
space:
mode:
authorKrzysztof Kozlowski <k.kozlowski@samsung.com>2015-04-07 22:28:50 +0900
committerInki Dae <inki.dae@samsung.com>2015-04-13 11:39:42 +0900
commit1c363c7cccf64128087002b0779986ad16aff6dc (patch)
tree1f1188f0361bf0acde927ae5c4e0cb3843169f19 /include/video/sh_mobile_lcdc.h
parentd1222842c1c7c2760ebd412238d9bb6234e6742c (diff)
downloadlinux-stable-1c363c7cccf64128087002b0779986ad16aff6dc.tar.gz
linux-stable-1c363c7cccf64128087002b0779986ad16aff6dc.tar.bz2
linux-stable-1c363c7cccf64128087002b0779986ad16aff6dc.zip
drm/exynos: Enable DP clock to fix display on Exynos5250 and other
After adding display power domain for Exynos5250 in commit 2d2c9a8d0a4f ("ARM: dts: add display power domain for exynos5250") the display on Chromebook Snow and others stopped working after boot. The reason for this suggested Andrzej Hajda: the DP clock was disabled. This clock is required by Display Port and is enabled by bootloader. However when FIMD driver probing was deferred, the display power domain was turned off. This effectively reset the value of DP clock enable register. When exynos-dp is later probed, the clock is not enabled and display is not properly configured: exynos-dp 145b0000.dp-controller: Timeout of video streamclk ok exynos-dp 145b0000.dp-controller: unable to config video Fixes: 2d2c9a8d0a4f ("ARM: dts: add display power domain for exynos5250") Cc: <stable@vger.kernel.org> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> Reported-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Tested-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Tested-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Inki Dae <inki.dae@samsung.com>
Diffstat (limited to 'include/video/sh_mobile_lcdc.h')
0 files changed, 0 insertions, 0 deletions