public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com, ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Cancel vdd off work before suspend
Date: Wed, 26 Nov 2014 17:01:23 +0200	[thread overview]
Message-ID: <87bnnuqa4c.fsf@intel.com> (raw)
In-Reply-To: <1416926287.12788.36.camel@intelbox>

On Tue, 25 Nov 2014, Imre Deak <imre.deak@intel.com> wrote:
> On Tue, 2014-11-25 at 15:43 +0200, ville.syrjala@linux.intel.com wrote:
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> 
>> Currently we just make sure vdd is off before suspending, but we don't
>> cancel the vdd off work. The work wil not touch vdd if
>> want_panel_vdd==false so in theory this is fine.
>> 
>> In the past that was perfectly fine since the vdd off work didn't do
>> anything when want_panel_vdd==false, so even if the work would have been
>> run during system resume before i915 has resumed, nothing would happen.
>> 
>> However since pps_lock() will now grab the power domain references before
>> it can check want_panel_vdd, we may end up toggling the power wells on/off
>> already before the driver has resumed. That is not really acceptable, so
>> cancel the vdd off work when suspending the encoder.
>> 
>> The problem appeared when pps_lock() was introduced in:
>>  commit 773538e86081d146e0020435d614f4b96996c1f9
>>  Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>  Date:   Thu Sep 4 14:54:56 2014 +0300
>> 
>>     drm/i915: Reset power sequencer pipe tracking when disp2d is off
>> 
>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Imre Deak <imre.deak@intel.com>

Pushed to drm-intel-fixes, thanks for the patch and review.

BR,
Jani.

>
>> ---
>>  drivers/gpu/drm/i915/intel_dp.c | 1 +
>>  1 file changed, 1 insertion(+)
>> 
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 46731da..d2529ec 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -4335,6 +4335,7 @@ static void intel_dp_encoder_suspend(struct intel_encoder *intel_encoder)
>>  	 * vdd might still be enabled do to the delayed vdd off.
>>  	 * Make sure vdd is actually turned off here.
>>  	 */
>> +	cancel_delayed_work_sync(&intel_dp->panel_vdd_work);
>>  	pps_lock(intel_dp);
>>  	edp_panel_vdd_off_sync(intel_dp);
>>  	pps_unlock(intel_dp);
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-11-26 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 13:43 [PATCH] drm/i915: Cancel vdd off work before suspend ville.syrjala
2014-11-25 14:38 ` Imre Deak
2014-11-26 15:01   ` Jani Nikula [this message]
2014-11-26 11:29 ` shuang.he

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bnnuqa4c.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox