diff options
| author |   Paulo Zanoni <paulo.r.zanoni@intel.com> | 2013-08-02 16:22:24 -0300 |
|---|---|---|
| committer |   Daniel Vetter <daniel.vetter@ffwll.ch> | 2013-08-22 13:31:47 +0200 |
| commit | 8dc8a27c9733a41cda84e8c70da8313e1d54c4ae (patch) | |
| tree | c3a66bc3b8a05e76a457737ce93d0b8a3da3f5cc /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/i915: Drop the overzealous warning from i915_gem_set_cache_level (diff) | |
| download | linux-dev-8dc8a27c9733a41cda84e8c70da8313e1d54c4ae.tar.xz linux-dev-8dc8a27c9733a41cda84e8c70da8313e1d54c4ae.zip | |
drm/i915: check the power well when redisabling VGA
If the power well is disabled VGA is guaranteed to be disabled.
This fixes unclaimed register messages that happen on suspend/resume.
v2: Check the actual hw power well state instead of our own tracking
to make sure VGA is _really_ off (in case the BIOS/KVMr has just its
own request bit set). Requested by Ville.
Note: Ville suggested whether it wouldn't be better to just enable the
power well over a slightly longer time in our resume code, since we
already do that. I tend to agree, but there's also the modeset force
code in the lid notifier which _also_ eventually calls redisable_vga.
We shouldn't ever need this on somewhat modern hw (everything with
opregion essentially) but the code to bail out isn't there. Hence
stick with this simple approach here for now.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=67517
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
[danvet: Summarize the discussion around the resume sequence and lid
notifier a bit.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions