[Bug 98695] [byt bisected] WARN_ON(!power_domains->domain_use_count[domain])
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Nov 14 11:23:37 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98695
--- Comment #7 from yann <yann.argotti at intel.com> ---
(In reply to Matwey V. Kornilov from comment #6)
> (In reply to yann from comment #4)
> > (In reply to Chris Wilson from comment #3)
> > > commit a781ce79d51fc4952870c998937980a042927e84
> > > Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
> > > Date: Fri Nov 27 18:55:25 2015 +0200
> > >
> > > drm/i915: Clean up AUX power domain handling
> > >
> > > Introduce intel_display_port_aux_power_domain() which simply returns
> > > the appropriate AUX power domain for a specific port, and then replace
> > > the intel_display_port_power_domain() with calls to the new function
> > > in the DP code. As long as we're not actually enabling the port we don't
> > > need the lane power domains, and those are handled now purely from
> > > modeset_update_crtc_power_domains().
> > >
> > > My initial motivation for this was to see if I could keep the DPIO power
> > > wells powered down while doing AUX on CHV, but turns out I can't so this
> > > doesn't change anything for CHV at least. But I think it's still a
> > > worthwile change.
> >
> > Matwey, please re-test with latest drm-intel-nightly
> > (https://cgit.freedesktop.org/drm-intel/) and confirm that is now fixed also
> > on your side.
>
> Ok, I will do. Should I pay extra attention to the specific commit which you
> believe fix the issue.
The goal is to have a version where that commit is merged. If you take latest
drm-intel-nightly, for instance, you should be safe because it already merged
in that branch
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161114/1bc338b9/attachment.html>
More information about the intel-gfx-bugs
mailing list