Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Lan, Hai" <hai.lan@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v6
Date: Thu, 23 Feb 2012 09:01:36 -0800	[thread overview]
Message-ID: <20120223090136.597a4864@jbarnes-desktop> (raw)
In-Reply-To: <6EEEFEA51F031E4EA5EF3AB55941C5F00FCDD377@SHSMSX102.ccr.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --]

On Wed, 15 Feb 2012 03:18:42 +0000
"Lan, Hai" <hai.lan@intel.com> wrote:

> Hi Jesse,
> I have tested the video sprite with intel-gpu-tools on SNB and found a bug.
> When setting overlay position with x<0, it will divide 0 and make drm driver crash. 
> I have fixed it. Please see my patch. Thanks.
> 
> Hai Lan
> 
> > -----Original Message-----
> > From: intel-gfx-bounces+hai.lan=intel.com@lists.freedesktop.org
> > [mailto:intel-gfx-bounces+hai.lan=intel.com@lists.freedesktop.org] On
> > Behalf Of Jesse Barnes
> > Sent: Wednesday, December 14, 2011 5:20 AM
> > To: intel-gfx@lists.freedesktop.org
> > Subject: [Intel-gfx] [PATCH 1/3] drm/i915: add SNB and IVB video sprite
> > support v6
> > 
> > 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.
> 
> 
> > +static bool
> > +sandybridge_compute_sprite_srwm(struct drm_device *dev, int plane,
> > +				uint32_t sprite_width, int pixel_size,
> > +				const struct intel_watermark_params *display,
> > +				int latency_ns, int *sprite_wm)
> > +{
> > +	struct drm_crtc *crtc;
> > +	unsigned long line_time_us;
> > +	int clock;
> > +	int line_count, line_size;
> > +	int small, large;
> > +	int entries;
> > +
> > +	if (!latency_ns) {
> > +		*sprite_wm = 0;
> > +		return false;
> > +	}
> > +
> > +	crtc = intel_get_crtc_for_plane(dev, plane);
> > +	clock = crtc->mode.clock;
> > +
> > +	line_time_us = (sprite_width * 1000) / clock;
> > +	line_count = (latency_ns / line_time_us + 1000) / 1000;
> > +	line_size = sprite_width * pixel_size;
> > +
> 

Applied, thanks Hai.

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2012-02-23 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 21:19 [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v6 Jesse Barnes
2011-12-13 21:19 ` [PATCH 2/3] drm/i915: track sprite coverage and disable primary plane if possible Jesse Barnes
2011-12-13 21:19 ` [PATCH 3/3] drm/i915: add color key support v3 Jesse Barnes
2011-12-13 22:09   ` [PATCH] drm/i915: add color key support v4 Jesse Barnes
2011-12-13 23:00     ` Daniel Vetter
2012-02-15  3:18 ` [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v6 Lan, Hai
2012-02-23 17:01   ` 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=20120223090136.597a4864@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=hai.lan@intel.com \
    --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