public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v5
Date: Mon, 12 Dec 2011 22:56:34 +0100	[thread overview]
Message-ID: <20111212215634.GB6832@phenom.ffwll.local> (raw)
In-Reply-To: <1323289763-1963-2-git-send-email-jbarnes@virtuousgeek.org>

On Wed, Dec 07, 2011 at 12:29:21PM -0800, Jesse Barnes wrote:
> The video sprites support various video surface formats natively and can
> handle scaling as well.  So add support for them using the new DRM core
> sprite support functions.
> 
> v2: use drm specific fourcc header and defines
> v3: address Daniel's comments:
>   - don't take struct mutex around register access (only needed for
>     regs in the GT power well)
>   - don't hold struct mutex across vblank waits
>   - fix up update_plane API (pass obj instead of GTT offset)
>   - add interlaced defines for sprite regs
>   - drop unnecessary 'reg' variables
>   - comment double buffered reg flushing
>   Also fix w/h confusion when writing the scaling reg.
> v4: more fixes, address more comments from Daniel, and include Hai's fix
>   - prevent divide by zero in scaling calculation (Hai Lan)
>   - update to Ville's new DRM_FORMAT_* types
>   - fix sprite watermark handling (calc based on CRTC size, separate
>     from normal display wm)
>   - remove private refcounts now that the fb cleanups handles things
> v5: add linear surface support
> 
> For this version, I tested DPMS since it came up in the last review;
> DPMS off/on works ok when a video player is working under X, but for
> power saving we'll probably want to do something smarter.  I'll leave
> that for a separate patch on top.  Likewise with the refcounting/fb
> layer handling, which are really separate cleanups.
> 
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

I didn't bother to recheck the regs and and the wm stuff looks like the
usual magic ;-) Otherwise you've implemented way more of my review
comments than I could possibly still remember, so it must be good.

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2011-12-12 21:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 20:29 Plane support for SNB and IVB Jesse Barnes
2011-12-07 20:29 ` [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v5 Jesse Barnes
2011-12-12 21:56   ` Daniel Vetter [this message]
2011-12-13 19:46     ` Jesse Barnes
2011-12-13 21:11     ` Jesse Barnes
2011-12-07 20:29 ` [PATCH 2/3] drm/i915: add destination color key support Jesse Barnes
2011-12-12 22:14   ` Daniel Vetter
2011-12-07 20:29 ` [PATCH 3/3] drm/i915: track sprite coverage and disable primary plane if possible Jesse Barnes
2011-12-12 22:17   ` Daniel Vetter
2011-12-08  2:58 ` Plane support for SNB and IVB Hai Lan
2011-12-12 21:21 ` 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=20111212215634.GB6832@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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