* [PATCH] drm/i915: FBC needs vblank before enable / disable.
@ 2019-04-03 4:30 kiran.s.kumar
2019-04-03 4:52 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC needs vblank before enable / disable. (rev2) Patchwork
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: kiran.s.kumar @ 2019-04-03 4:30 UTC (permalink / raw)
To: intel-gfx
From: Kiran Kumar S <kiran.s.kumar@intel.corp-partner.google.com>
As per the display workaround #1200, FBC needs wait for vblank before
enabling and before disabling FBC.
In some cases, depending on whether FBC was compressing in that frame,
several control signals in the compression engine also will fail to properly
recognize the final segment of the frame as a result of the missing last
pixel indication. As a result of this, we're seeing corrupted cache
line/compression indicators after FBC re-enables which causes underruns or
corruption when they're used to decompress.
WA sequence as below:
1) Display enables plane 1A
2) Wait for 1 vblank
3) FBC gets enabled
4) Wait for 1 VBLANK
5) Turn off FBC
In GLK Chrome OS, if FBC is enabled by default, few top lines on the screen
got corrupted. With the above WA, issue was resolved.
Change-Id: I2465610bb0a82df99e5c53b1eb4ed74565996b1e
Signed-off-by: Kiran Kumar S <kiran.s.kumar@intel.corp-partner.google.com>
---
drivers/gpu/drm/i915/intel_display.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 8576a7f799f2..5118a36782eb 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -13207,8 +13207,11 @@ static void intel_update_crtc(struct drm_crtc *crtc,
if (pipe_config->update_pipe && !pipe_config->enable_fbc)
intel_fbc_disable(intel_crtc);
- else if (new_plane_state)
+ else if (new_plane_state) {
+ /* Display WA #1200: GLK */
+ intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
intel_fbc_enable(intel_crtc, pipe_config, new_plane_state);
+ }
intel_begin_crtc_commit(crtc, old_crtc_state);
@@ -13419,6 +13422,8 @@ static void intel_atomic_commit_tail(struct drm_atomic_state *state)
dev_priv->display.crtc_disable(old_intel_crtc_state, state);
intel_crtc->active = false;
+ /* Display WA #1200: GLK */
+ intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
intel_fbc_disable(intel_crtc);
intel_disable_shared_dpll(old_intel_crtc_state);
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 4+ messages in thread* ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC needs vblank before enable / disable. (rev2)
2019-04-03 4:30 [PATCH] drm/i915: FBC needs vblank before enable / disable kiran.s.kumar
@ 2019-04-03 4:52 ` Patchwork
2019-04-03 5:10 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-03 17:54 ` [PATCH] drm/i915: FBC needs vblank before enable / disable Souza, Jose
2 siblings, 0 replies; 4+ messages in thread
From: Patchwork @ 2019-04-03 4:52 UTC (permalink / raw)
To: kiran.s.kumar; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: FBC needs vblank before enable / disable. (rev2)
URL : https://patchwork.freedesktop.org/series/58843/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a7eb63398cfa drm/i915: FBC needs vblank before enable / disable.
-:10: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#10:
several control signals in the compression engine also will fail to properly
-:26: ERROR:GERRIT_CHANGE_ID: Remove Gerrit Change-Id's before submitting upstream.
#26:
Change-Id: I2465610bb0a82df99e5c53b1eb4ed74565996b1e
total: 1 errors, 1 warnings, 0 checks, 20 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 4+ messages in thread
* ✗ Fi.CI.BAT: failure for drm/i915: FBC needs vblank before enable / disable. (rev2)
2019-04-03 4:30 [PATCH] drm/i915: FBC needs vblank before enable / disable kiran.s.kumar
2019-04-03 4:52 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC needs vblank before enable / disable. (rev2) Patchwork
@ 2019-04-03 5:10 ` Patchwork
2019-04-03 17:54 ` [PATCH] drm/i915: FBC needs vblank before enable / disable Souza, Jose
2 siblings, 0 replies; 4+ messages in thread
From: Patchwork @ 2019-04-03 5:10 UTC (permalink / raw)
To: kiran.s.kumar; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: FBC needs vblank before enable / disable. (rev2)
URL : https://patchwork.freedesktop.org/series/58843/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5860 -> Patchwork_12664
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_12664 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_12664, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://patchwork.freedesktop.org/api/1.0/series/58843/revisions/2/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12664:
### IGT changes ###
#### Possible regressions ####
* igt@debugfs_test@read_all_entries:
- fi-byt-j1900: PASS -> DMESG-WARN
* igt@gem_exec_suspend@basic-s3:
- fi-kbl-r: PASS -> DMESG-WARN
- fi-skl-lmem: PASS -> DMESG-WARN
- fi-bdw-gvtdvm: PASS -> DMESG-WARN
- fi-skl-iommu: PASS -> DMESG-WARN
- fi-icl-u2: PASS -> DMESG-WARN
- fi-bsw-kefka: PASS -> DMESG-WARN
- fi-byt-clapper: PASS -> DMESG-WARN
- fi-skl-gvtdvm: PASS -> DMESG-WARN
- fi-icl-u3: PASS -> DMESG-WARN
- fi-skl-6600u: PASS -> DMESG-WARN
* igt@runner@aborted:
- fi-ilk-650: NOTRUN -> FAIL
- fi-pnv-d510: NOTRUN -> FAIL
- fi-bdw-gvtdvm: NOTRUN -> FAIL
- fi-hsw-peppy: NOTRUN -> FAIL
- fi-icl-u2: NOTRUN -> FAIL
- fi-snb-2520m: NOTRUN -> FAIL
- fi-hsw-4770: NOTRUN -> FAIL
- fi-whl-u: NOTRUN -> FAIL
- fi-icl-u3: NOTRUN -> FAIL
- fi-ivb-3770: NOTRUN -> FAIL
- fi-byt-j1900: NOTRUN -> FAIL
- fi-bsw-n3050: NOTRUN -> FAIL
- fi-blb-e6850: NOTRUN -> FAIL
- fi-bsw-kefka: NOTRUN -> FAIL
- fi-hsw-4770r: NOTRUN -> FAIL
- fi-byt-clapper: NOTRUN -> FAIL
- fi-bdw-5557u: NOTRUN -> FAIL
- fi-bwr-2160: NOTRUN -> FAIL
- fi-byt-n2820: NOTRUN -> FAIL
- fi-elk-e7500: NOTRUN -> FAIL
Known issues
------------
Here are the changes found in Patchwork_12664 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@runner@aborted:
- fi-cfl-8109u: NOTRUN -> FAIL [k.org#202107] / [k.org#202109]
- fi-bxt-j4205: NOTRUN -> FAIL [fdo#109516]
- fi-skl-iommu: NOTRUN -> FAIL [fdo#104108]
- fi-cfl-guc: NOTRUN -> FAIL [k.org#202107] / [k.org#202109]
- fi-kbl-7567u: NOTRUN -> FAIL [fdo#108903] / [fdo#108904] / [fdo#108905]
- fi-skl-guc: NOTRUN -> FAIL [fdo#104108]
- fi-skl-6700k2: NOTRUN -> FAIL [fdo#104108]
- fi-kbl-x1275: NOTRUN -> FAIL [fdo#108903] / [fdo#108904] / [fdo#108905]
- fi-cfl-8700k: NOTRUN -> FAIL [k.org#202107] / [k.org#202109]
- fi-skl-6600u: NOTRUN -> FAIL [fdo#104108]
- fi-skl-lmem: NOTRUN -> FAIL [fdo#104108]
- fi-kbl-r: NOTRUN -> FAIL [fdo#109383]
- fi-skl-6770hq: NOTRUN -> FAIL [fdo#104108]
- fi-skl-gvtdvm: NOTRUN -> FAIL [fdo#104108]
- fi-snb-2600: NOTRUN -> FAIL [fdo#108929]
#### Warnings ####
* igt@gem_exec_suspend@basic-s3:
- fi-whl-u: FAIL [fdo#103375] -> DMESG-FAIL [fdo#103375]
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#108903]: https://bugs.freedesktop.org/show_bug.cgi?id=108903
[fdo#108904]: https://bugs.freedesktop.org/show_bug.cgi?id=108904
[fdo#108905]: https://bugs.freedesktop.org/show_bug.cgi?id=108905
[fdo#108929]: https://bugs.freedesktop.org/show_bug.cgi?id=108929
[fdo#109383]: https://bugs.freedesktop.org/show_bug.cgi?id=109383
[fdo#109516]: https://bugs.freedesktop.org/show_bug.cgi?id=109516
[k.org#202107]: https://bugzilla.kernel.org/show_bug.cgi?id=202107
[k.org#202109]: https://bugzilla.kernel.org/show_bug.cgi?id=202109
Participating hosts (46 -> 41)
------------------------------
Additional (2): fi-hsw-4770r fi-snb-2600
Missing (7): fi-kbl-soraka fi-ilk-m540 fi-byt-squawks fi-ctg-p8600 fi-gdg-551 fi-icl-y fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_5860 -> Patchwork_12664
CI_DRM_5860: 837ba3cd997b59e53903ba29f4fe65c81f86f1e9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4923: 6285eec4f3b8f21833d9d2d852883569d6551822 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12664: a7eb63398cfaf8859aa249e273117fdda6bb8523 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a7eb63398cfa drm/i915: FBC needs vblank before enable / disable.
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12664/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] drm/i915: FBC needs vblank before enable / disable.
2019-04-03 4:30 [PATCH] drm/i915: FBC needs vblank before enable / disable kiran.s.kumar
2019-04-03 4:52 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC needs vblank before enable / disable. (rev2) Patchwork
2019-04-03 5:10 ` ✗ Fi.CI.BAT: failure " Patchwork
@ 2019-04-03 17:54 ` Souza, Jose
2 siblings, 0 replies; 4+ messages in thread
From: Souza, Jose @ 2019-04-03 17:54 UTC (permalink / raw)
To: intel-gfx@lists.freedesktop.org, Kumar, Kiran S
[-- Attachment #1.1: Type: text/plain, Size: 2503 bytes --]
On Wed, 2019-04-03 at 10:00 +0530, kiran.s.kumar@intel.com wrote:
> From: Kiran Kumar S <kiran.s.kumar@intel.corp-partner.google.com>
>
> As per the display workaround #1200, FBC needs wait for vblank before
> enabling and before disabling FBC.
>
> In some cases, depending on whether FBC was compressing in that
> frame,
> several control signals in the compression engine also will fail to
> properly
> recognize the final segment of the frame as a result of the missing
> last
> pixel indication. As a result of this, we're seeing corrupted cache
> line/compression indicators after FBC re-enables which causes
> underruns or
> corruption when they're used to decompress.
>
> WA sequence as below:
> 1) Display enables plane 1A
> 2) Wait for 1 vblank
> 3) FBC gets enabled
> 4) Wait for 1 VBLANK
> 5) Turn off FBC
>
> In GLK Chrome OS, if FBC is enabled by default, few top lines on the
> screen
> got corrupted. With the above WA, issue was resolved.
>
> Change-Id: I2465610bb0a82df99e5c53b1eb4ed74565996b1e
> Signed-off-by: Kiran Kumar S <
> kiran.s.kumar@intel.corp-partner.google.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 8576a7f799f2..5118a36782eb 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -13207,8 +13207,11 @@ static void intel_update_crtc(struct
> drm_crtc *crtc,
>
> if (pipe_config->update_pipe && !pipe_config->enable_fbc)
> intel_fbc_disable(intel_crtc);
> - else if (new_plane_state)
> + else if (new_plane_state) {
> + /* Display WA #1200: GLK */
> + intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
Wait a vblank of partially changed state? That is not a good idea at
all.
Also it would wait a vblank even if FBC is not enabled.
> intel_fbc_enable(intel_crtc, pipe_config,
> new_plane_state);
> + }
>
> intel_begin_crtc_commit(crtc, old_crtc_state);
>
> @@ -13419,6 +13422,8 @@ static void intel_atomic_commit_tail(struct
> drm_atomic_state *state)
>
> dev_priv-
> >display.crtc_disable(old_intel_crtc_state, state);
> intel_crtc->active = false;
> + /* Display WA #1200: GLK */
> + intel_wait_for_vblank(dev_priv, intel_crtc-
> >pipe);
> intel_fbc_disable(intel_crtc);
> intel_disable_shared_dpll(old_intel_crtc_state)
> ;
>
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-04-03 17:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-04-03 4:30 [PATCH] drm/i915: FBC needs vblank before enable / disable kiran.s.kumar
2019-04-03 4:52 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC needs vblank before enable / disable. (rev2) Patchwork
2019-04-03 5:10 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-03 17:54 ` [PATCH] drm/i915: FBC needs vblank before enable / disable Souza, Jose
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox