diff options
author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-07-10 09:50:11 +0200 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-09-06 08:21:30 +0200 |
commit | 8af6cf88a5ad7fa41d4eb700cc97f01d0bcd2a69 (patch) | |
tree | 97475031324a623e4f46fd8ce8a4db706d26b116 /drivers/gpu/drm/i915/intel_dvo.c | |
parent | 9dc10f37e326d5d789929e1886b5a8089ccee5a7 (diff) | |
download | linux-3.10-8af6cf88a5ad7fa41d4eb700cc97f01d0bcd2a69.tar.gz linux-3.10-8af6cf88a5ad7fa41d4eb700cc97f01d0bcd2a69.tar.bz2 linux-3.10-8af6cf88a5ad7fa41d4eb700cc97f01d0bcd2a69.zip |
drm/i915: add tons of modeset state checks
... let's see whether this catches anything earlier and I can track
down a few bugs.
v2: Add more checks and also add DRM_DEBUG_KMS output so that it's
clear which connector/encoder/crtc is being checked atm. Which proved
rather useful for debugging ...
v3: Add a WARN in the common encoder dpms function, now that also
modeset changes properly update the dpms state ...
v4: Properly add a short explanation for each WARN, to avoid the need
to correlate dmesg lines with source lines accurately. Suggested by
Chris Wilson.
v5: Also dump (expected, found) for state checks (or wherever it's not
apparent from the test what exactly mismatches with expectations).
Again suggested by Chris Wilson.
v6: Due to an issue reported by Paulo Zanoni I've noticed that the
encoder checking is by far not as strict as it could and should be.
Improve this.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_dvo.c')
0 files changed, 0 insertions, 0 deletions