diff options
| author | Deepak Rawat <drawat@vmware.com> | 2018-08-09 14:22:12 -0700 |
|---|---|---|
| committer | Deepak Rawat <drawat@vmware.com> | 2018-08-16 15:22:09 -0700 |
| commit | 65c381c13da1475458412195ba9c442376fea0a4 (patch) | |
| tree | 0bf8ec4eb1909f05a0f9225134c26b26fc02ff5d | |
| parent | 0668b6f7d41f6af18cc7da8e3e2d969620140dc4 (diff) | |
vmwgfx: don't check for old_crtc_state enable status
During atomic check to prepare the new topology no need to check if
old_crtc_state was enabled or not. This will cause atomic_check to fail
because due to connector routing a crtc can be in atomic_state even if
there was no change to enable status.
Detected this issue with igt run.
Signed-off-by: Deepak Rawat <drawat@vmware.com>
Reviewed-by: Sinclair Yeh <syeh@vmware.com>
| -rw-r--r-- | vmwgfx_kms.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/vmwgfx_kms.c b/vmwgfx_kms.c index 8b6891b..a16da3b 100644 --- a/vmwgfx_kms.c +++ b/vmwgfx_kms.c @@ -1651,7 +1651,7 @@ static int vmw_kms_check_topology(struct drm_device *dev, struct drm_connector_state *conn_state; struct vmw_connector_state *vmw_conn_state; - if (!new_crtc_state->enable && old_crtc_state->enable) { + if (!new_crtc_state->enable) { rects[i].x1 = 0; rects[i].y1 = 0; rects[i].x2 = 0; |