tree 357bb467379fee59c9b2b167ae2a38331ee654b7
parent b846350aa272de99bf6fecfa6b08e64ebfb13173
author Marek Szyprowski <m.szyprowski@samsung.com> 1750248386 +0200
committer Inki Dae <inki.dae@samsung.com> 1751183896 +0900
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQGzBAABCgAdFiEEoxi+6c5pRPV/gdXcxWAb7Og/+bYFAmhg8hgACgkQxWAb7Og/
 +bbD+wwAy5GS1bn9qzvXKYEU1Ry6OpwYRNktY1fIWhA2/arOsTXpy6W3Qy/jINpp
 4jRzKn6rgvdjNKWjPKdB9ArDxt1RNDgxKT+SPCXDY28GumFS2p9n8WTkvB+ydyOP
 xO3OHqI0+uH9ksvLYty8yPbT1orA2ht+dW16QyX6p/3u9DlotqRPv2UlOx6jhWNc
 9HlUukvMUF5ElUHqA3upMTu8nIvoang9LmcKyRNeNd+2OlBQBIJP+EtAGI2tUDjZ
 jLJt3rscpRypJlyxN3GC+1e9I3rAU7WDJxEKoORK0cDboaE/5niWf+wxVCHcRVvH
 ORPJdPGIgGFRkcRVB0PMDqlL8x2zg4jkmg+BeGGYOHVCWR3sfpATc2eTBpaBOevl
 ss+M5POrZc+Y0XaJXzCd9hPL5h0rpLsxPtQ8TnMsLhqMAll3HfyrQMwgmWMrm1rn
 p0CF2zTyGyLKILJbKoYtH+Xg3wjKPudX6yU7hQIYYTKQhAla7PBrrkAq64D0OE3M
 XuC8C2R3
 =BA7V
 -----END PGP SIGNATURE-----

drm/exynos: fimd: Guard display clock control with runtime PM calls

Commit c9b1150a68d9 ("drm/atomic-helper: Re-order bridge chain pre-enable
and post-disable") changed the call sequence to the CRTC enable/disable
and bridge pre_enable/post_disable methods, so those bridge methods are
now called when CRTC is not yet enabled.

This causes a lockup observed on Samsung Peach-Pit/Pi Chromebooks. The
source of this lockup is a call to fimd_dp_clock_enable() function, when
FIMD device is not yet runtime resumed. It worked before the mentioned
commit only because the CRTC implemented by the FIMD driver was always
enabled what guaranteed the FIMD device to be runtime resumed.

This patch adds runtime PM guards to the fimd_dp_clock_enable() function
to enable its proper operation also when the CRTC implemented by FIMD is
not yet enabled.

Fixes: 196e059a8a6a ("drm/exynos: convert clock_enable crtc callback to pipeline clock")
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>