From: Daniel Vetter <daniel@ffwll.ch>
To: "Bloomfield, Jon" <jon.bloomfield@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Introduce vblank work function
Date: Fri, 6 Dec 2013 13:06:54 +0100 [thread overview]
Message-ID: <20131206120653.GI27344@phenom.ffwll.local> (raw)
In-Reply-To: <AD48BB7FB99B174FBCC69E228F58B3B601560A5C@IRSMSX103.ger.corp.intel.com>
On Fri, Dec 06, 2013 at 10:44:15AM +0000, Bloomfield, Jon wrote:
> What's the status of this patch ? I can't find any subsequent mention of
> it, but we currently use it in one of our Android development trees. I'm
> trying to work out whether to retain it or replace it.
>
> Was it killed off, or is it still in the pipeline ?
Stalled atm I think. The overall concept of a vblank worker/timer support
code is still useful imo. I think I've written up all the bikesheds
Chris&I discussed on irc in my other reply.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-12-06 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 22:07 RFC asynchronous vblank tasks Chris Wilson
2013-07-04 22:07 ` [PATCH 1/5] drm/i915: Asynchronously unpin the old framebuffer after the next vblank Chris Wilson
2013-07-04 22:07 ` [PATCH 2/5] drm/i915/sprite: Make plane switching asynchronous Chris Wilson
2013-07-04 22:07 ` [PATCH 3/5] drm/i915: Synchronize userspace palette LUT (i.e. gamma) changes to vblank Chris Wilson
2013-07-04 22:07 ` [PATCH 4/5] drm/i915: Up/downclock LVDS on vblanks Chris Wilson
2013-07-04 22:07 ` [PATCH 5/5] drm/i915: Boost DMA qos whilst performing uninterruptible waits for the GPU Chris Wilson
2013-07-05 8:42 ` RFC asynchronous vblank tasks Daniel Vetter
2013-07-05 8:48 ` [PATCH] drm/i915: Introduce vblank work function Chris Wilson
2013-12-06 10:44 ` Bloomfield, Jon
2013-12-06 12:06 ` Daniel Vetter [this message]
2013-12-06 12:12 ` Bloomfield, Jon
2013-12-06 13:42 ` Daniel Vetter
2013-12-06 16:49 ` Jesse Barnes
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=20131206120653.GI27344@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jon.bloomfield@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