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: intel_update_fbc() requires struct_mutex, so no longer atomic
Date: Tue, 17 Apr 2012 08:49:06 -0700 [thread overview]
Message-ID: <20120417084906.7de696f0@jbarnes-desktop> (raw)
In-Reply-To: <1334671699-11631-1-git-send-email-chris@chris-wilson.co.uk>
On Tue, 17 Apr 2012 15:08:19 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> As we need to manipulate our device structure and allocate queue a task,
> it is no longer a simple atomic operation and cannot be performed along
> the atomic modeset paths. Instead make sure that we disable FBC (which
> must be therefore kept as a set of simple register writes) when
> performing the atomic modeset and leave the heavy-weight
> intel_update_fbc() for the normal modeset.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> ---
Looks good.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
next prev parent reply other threads:[~2012-04-17 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 14:08 [PATCH] drm/i915: intel_update_fbc() requires struct_mutex, so no longer atomic Chris Wilson
2012-04-17 15:49 ` Jesse Barnes [this message]
2012-04-18 10:02 ` 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=20120417084906.7de696f0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox