All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: cancel the panel VDD work when we do it manually
Date: Thu, 31 Oct 2013 14:46:43 +0200	[thread overview]
Message-ID: <87wqktppzg.fsf@intel.com> (raw)
In-Reply-To: <20131031111119.GH4167@phenom.ffwll.local>

On Thu, 31 Oct 2013, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Oct 30, 2013 at 07:50:28PM -0200, Paulo Zanoni wrote:
>> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>> 
>> After I reorganized the panel VDD debug messages I was able to spot we
>> were disabling it one extra time. The problem is that we're missing
>> the call to cancel the delayed work in one of the instances where we
>> manually call ironlake_panel_vdd_off_sync().
>> 
>> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>> ---
>>  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 8db1fda..f2280b4 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -1159,6 +1159,7 @@ void ironlake_edp_panel_vdd_off(struct intel_dp *intel_dp, bool sync)
>>  	intel_dp->want_panel_vdd = false;
>>  
>>  	if (sync) {
>> +		cancel_delayed_work_sync(&intel_dp->panel_vdd_work);
>
> This will deadlock since we hold the mode_config.mutex here, and the
> panel_vdd_work also needs that. I've merged the other two patches.

Ooof, reviewer facepalm.

So we are calling ironlake_panel_vdd_off_sync() twice in this path, but
that shouldn't matter, as we have

if (!intel_dp->want_panel_vdd && ironlake_edp_have_panel_vdd(intel_dp))

in there, right? Paulo, is that what you're seeing, or something else?


BR,
Jani.



> -Daniel
>
>>  		ironlake_panel_vdd_off_sync(intel_dp);
>>  	} else {
>>  		/*
>> -- 
>> 1.8.3.1
>> 
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2013-10-31 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 21:50 [PATCH 1/3] drm/i915: turn the eDP VDD on for any i2c transactions Paulo Zanoni
2013-10-30 21:50 ` [PATCH 2/3] drm/i915: reduce eDP VDD message verbose Paulo Zanoni
2013-10-30 21:50 ` [PATCH 3/3] drm/i915: cancel the panel VDD work when we do it manually Paulo Zanoni
2013-10-31 11:11   ` Daniel Vetter
2013-10-31 12:46     ` Jani Nikula [this message]
2013-10-31 13:15       ` Paulo Zanoni
2013-10-31 14:13       ` Daniel Vetter
2013-10-31  8:14 ` [PATCH 1/3] drm/i915: turn the eDP VDD on for any i2c transactions Jani Nikula

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=87wqktppzg.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=przanoni@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.