From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: make CRTC enable/disable asynchronous v3
Date: Fri, 30 May 2014 15:10:03 -0700 [thread overview]
Message-ID: <20140530151003.631d073b@jbarnes-desktop> (raw)
In-Reply-To: <20140530220218.GF10916@nuc-i3427.alporthouse.com>
On Fri, 30 May 2014 23:02:18 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, May 30, 2014 at 02:28:52PM -0700, Jesse Barnes wrote:
> > @@ -10326,7 +10466,7 @@ static int __intel_set_mode(struct drm_crtc *crtc,
> >
> > for_each_intel_crtc_masked(dev, prepare_pipes, intel_crtc) {
> > if (intel_crtc->base.enabled)
> > - dev_priv->display.crtc_disable(&intel_crtc->base);
> > + intel_queue_crtc_disable(&intel_crtc->base);
> > }
>
> This one looks odd. prepare_pipes are the pipes we have to turn off in
> order to perform the modeset - which needs to be synchronous.
>
> intel_sync_crtcs(prepare_pipes) ?
Well, they'll happen in order. But I was just looking at this code and
in cases where ->mode_set messes with regs rather than staging it for
->crtc_enable we'll lose stuff here.
Until we have that, doing the disables for the prepare_pipe
synchronously is probably the right thing to do.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2014-05-30 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 18:05 [PATCH 1/2] drm/i915: make CRTC enable/disable asynchronous v2 Jesse Barnes
2014-05-30 18:05 ` [PATCH 2/2] drm/i915: make userspace mode sets asynchronous Jesse Barnes
2014-05-30 18:47 ` [PATCH 1/2] drm/i915: make CRTC enable/disable asynchronous v2 Chris Wilson
2014-05-30 18:50 ` Jesse Barnes
2014-05-30 18:53 ` Chris Wilson
2014-05-30 18:56 ` Chris Wilson
2014-05-30 19:06 ` Jesse Barnes
2014-05-30 21:28 ` [PATCH] drm/i915: make CRTC enable/disable asynchronous v3 Jesse Barnes
2014-05-30 22:02 ` Chris Wilson
2014-05-30 22:10 ` Jesse Barnes [this message]
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=20140530151003.631d073b@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--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 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.