[SKL] Disable display power well

Bug #1526220 reported by Timo Aaltonen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Timo Aaltonen
Vivid
Fix Released
Undecided
Unassigned
Wily
Won't Fix
Undecided
Unassigned

Bug Description

Display power well can cause issues like blank screen when logging in after resume from suspend, so it's best to disable it for now like upstream did in v4.4-rc1:

commit 1b0e3a049efe471c399674fd954500ce97438d30
Author: Imre Deak <email address hidden>
Date: Thu Nov 5 23:04:11 2015 +0200

    drm/i915/skl: disable display side power well support for now

    The display power well support on this platform is in a somewhat broken
    state atm, so disable it by default.

    This in effect will get rid of incorrect assert WARNs about the CSR/DMC
    firmware not being loaded during power well toggling. It also removes a
    problem during driver loading where a register is accessed while its
    backing power well is down, resulting in another WARN. Until we come up
    with the root cause of the second problem and the proper fix for both
    issues, keep all display side power wells on.

    Also clarify a bit the option description.

    Reported-by: Dave Airlie <email address hidden>
    Reference: http://mid<email address hidden>
    Signed-off-by: Imre Deak <email address hidden>
    Reviewed-by: Ville Syrjälä <email address hidden>
    Link: http://patchwork.freedesktop<email address hidden>
    Signed-off-by: Jani Nikula <email address hidden>

Timo Aaltonen (tjaalton)
Changed in linux (Ubuntu):
assignee: nobody → Timo Aaltonen (tjaalton)
status: New → Triaged
Changed in linux (Ubuntu Vivid):
status: New → Triaged
Changed in linux (Ubuntu Wily):
status: New → Triaged
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

as this just flips a switch on SKL it shouldn't require extensive regression testing on other hw

Luis Henriques (henrix)
Changed in linux (Ubuntu Vivid):
status: Triaged → Fix Committed
Revision history for this message
Luis Henriques (henrix) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-vivid
Revision history for this message
Phidias (phidias-chiang) wrote :

Fresh install Ubuntu 15.04:
Update kernel to 3.19.0-43 -> failed
Update kernel to 3.19.0-46 -> pass

The test is positive, change tag to verification-done-vivid

tags: added: verification-done-vivid
removed: verification-needed-vivid
Revision history for this message
Andy Whitcroft (apw) wrote :

Fix released in 3.19.0-47.53

Changed in linux (Ubuntu Vivid):
status: Fix Committed → Fix Released
Timo Aaltonen (tjaalton)
Changed in linux (Ubuntu):
status: Triaged → Fix Released
Changed in linux (Ubuntu Wily):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.