<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [byt bisected] WARN_ON(!power_domains->domain_use_count[domain])"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98695#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [byt bisected] WARN_ON(!power_domains->domain_use_count[domain])"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98695">bug 98695</a>
from <span class="vcard"><a class="email" href="mailto:yann.argotti@intel.com" title="yann <yann.argotti@intel.com>"> <span class="fn">yann</span></a>
</span></b>
<pre>(In reply to Matwey V. Kornilov from <a href="show_bug.cgi?id=98695#c6">comment #6</a>)
<span class="quote">> (In reply to yann from <a href="show_bug.cgi?id=98695#c4">comment #4</a>)
> > (In reply to Chris Wilson from <a href="show_bug.cgi?id=98695#c3">comment #3</a>)
> > > commit a781ce79d51fc4952870c998937980a042927e84
> > > Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
> > > 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
> > (<a href="https://cgit.freedesktop.org/drm-intel/">https://cgit.freedesktop.org/drm-intel/</a>) 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.</span >
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</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>