diff options
| author | Ville Syrjälä <[email protected]> | 2017-08-17 17:55:09 +0300 |
|---|---|---|
| committer | Ville Syrjälä <[email protected]> | 2017-08-25 14:44:38 +0300 |
| commit | 6e644626945c7c1a7f4d4f83b806b898297846d0 (patch) | |
| tree | 031e60f059b274712325b0f6f57d0c7fc8f4e4a1 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 3814fd77691c0b35acefc68d5af516f9d48a4281 (diff) | |
drm/i915: Beef up the IPS vs. CRC workaround
Oneshot disabling of IPS when CRC capturing is started is insufficient.
IPS may get re-enabled by any plane update, and hence tests that keep
CRC capturing on across plane updates will start to see inconsistent
results as soon as IPS kicks back in. Add a new knob into the crtc state
to make sure IPS stays disabled as long as CRC capturing is enabled.
Forcing a modeset is the easiest way to handle this since that's already
how we do the panel fitter workaround. It's a little heavy handed just
for IPS, but seeing as we might already do the panel fitter workaround
I think it's better to follow that. We migth want to optimize both cases
later if someone gets too upset by the extra delay from the modeset.
v2: Check the right thing when deciding whether to force a modeset
v3: Rebase, check HAS_IPS before forcing a modeset,
move ips_force_disable check into pipe_config_supports_ips()
Cc: Paulo Zanoni <[email protected]>
Cc: Daniel Vetter <[email protected]>
Cc: Maarten Lankhorst <[email protected]>
Cc: Marta Lofstedt <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101664
Reviewed-by: Paulo Zanoni <[email protected]>
Tested-by: Marta Lofsted <[email protected]> #v2
Signed-off-by: Ville Syrjälä <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions