diff options
| author |   Rodrigo Vivi <rodrigo.vivi@intel.com> | 2016-02-12 04:08:12 -0800 |
|---|---|---|
| committer | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2016-02-17 13:04:40 -0800 |
| commit | a38c274faad0ec6aba692e294ec751d04dbba803 (patch) | |
| tree | f45eca768c561e17b737c41d0f4226c392c8f4db /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | drm/i915: Change i915.enable_psr parameter to use per platform default. (diff) | |
| download | linux-dev-a38c274faad0ec6aba692e294ec751d04dbba803.tar.xz linux-dev-a38c274faad0ec6aba692e294ec751d04dbba803.zip | |
drm/i915: Enable PSR by default on Valleyview and Cherryview.
With a reliable frontbuffer tracking and all instability corner cases
solved for this platform let's re-enabled PSR by default.
In case a new issue is found and PSR is the main suspect, please check
if i915.enable_psr=0 really makes your problem go away,
please report it at bugs.freedesktop.org.
In a bugzilla entry for PSR is desirable:
- dmesg (drm.debug=0xe)
- output of /sys/kernel/debug/dri/0/i915_edp_psr_status
- Platform information. Vendor, model, id, pci id.
- Graphical environment: Gnome, KDE, openbox, etc...
- Details how to reproduce.
- Also good if you could run PSR test cases of Intel-gpu-tools
- Please mention if forcing main link standby or main link off helps you.
There are Intel-gpu-tools test cases that can be helpful to
determine if PSR is working as expected:
kms_psr_sink_crc and kms_psr_frontbuffer_tracking.
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions