summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/v3d
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ideasonboard.com>2023-11-09 09:38:04 +0200
committerTomi Valkeinen <tomi.valkeinen@ideasonboard.com>2023-12-01 12:04:43 +0200
commitca89b69734f92021e25899dff3e433b1904f5832 (patch)
treed5b8a877993c07a0ea92e9c3ff897d01537b6a97 /drivers/gpu/drm/v3d
parent95d4b471953411854f9c80b568da7fcf753f3801 (diff)
downloadlinux-ca89b69734f92021e25899dff3e433b1904f5832.tar.gz
linux-ca89b69734f92021e25899dff3e433b1904f5832.tar.bz2
linux-ca89b69734f92021e25899dff3e433b1904f5832.zip
drm/tidss: Use DRM_PLANE_COMMIT_ACTIVE_ONLY
At the moment the driver does not use DRM_PLANE_COMMIT_ACTIVE_ONLY, but still checks for crtc->state->active in tidss_crtc_atomic_flush(), and skips the flush if the crtc is not active. The exact reason why DRM_PLANE_COMMIT_ACTIVE_ONLY is not used has been lost in history. DRM_PLANE_COMMIT_ACTIVE_ONLY does also affect the plane updates, and I think the issue was related to multi-display systems and moving planes between the displays. However, it is possible the issue was only present on the older DSS hardware, handled by the omapdrm driver (on which the tidss driver is loosely based). Reviewing the code related to DRM_PLANE_COMMIT_ACTIVE_ONLY does not show any issues, and testing on J7 EVM with two displays works fine. Change the driver to use DRM_PLANE_COMMIT_ACTIVE_ONLY. Reviewed-by: Aradhya Bhatia <a-bhatia1@ti.com> Link: https://lore.kernel.org/r/20231109-tidss-probe-v2-11-ac91b5ea35c0@ideasonboard.com Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Diffstat (limited to 'drivers/gpu/drm/v3d')
0 files changed, 0 insertions, 0 deletions