Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: Flush any outstanding work to turn the VDD off
Date: Mon, 16 Apr 2012 23:53:18 +0200	[thread overview]
Message-ID: <20120416215318.GI4199@phenom.ffwll.local> (raw)
In-Reply-To: <1334610116_9592@CP5-2952>

On Mon, Apr 16, 2012 at 10:01:42PM +0100, Chris Wilson wrote:
> On Mon, 16 Apr 2012 22:39:51 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Mon, Apr 16, 2012 at 03:18:33PM +0100, Chris Wilson wrote:
> > > As we may kick off a delayed workqueue task to switch of the VDD lines, we
> > > need to complete that task prior to turning off the panel (which itself
> > > depends upon VDD being off).
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Keith Packard <keithp@keithp.com>
> > 
> > I've looked a bit at this and I think we just need a call to
> > ironlake_panel_vdd_off_sync instead of the WARN. The work will do the
> > right thing when the vdd is already off, so no problem there.
> 
> The WARN is valid and did help to document the design of the code.
> Good point about the cancel_sync taking the mutex again, oops, and
> indeed all we need here is just the call to sync.

Oops, yeah I've misread what want_panle_vdd means, the WARN looks good
as-is.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-04-16 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 14:18 [PATCH] drm/i915/dp: Flush any outstanding work to turn the VDD off Chris Wilson
2012-04-16 20:39 ` Daniel Vetter
2012-04-16 21:01   ` Chris Wilson
2012-04-16 21:53     ` Daniel Vetter [this message]
2012-04-16 21:43   ` Chris Wilson
2012-04-16 22:35     ` Daniel Vetter

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=20120416215318.GI4199@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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