All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Damien Lespiau <damien.lespiau@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Make num_sprites a per-pipe value
Date: Fri, 28 Feb 2014 20:15:38 +0200	[thread overview]
Message-ID: <20140228181538.GT3852@intel.com> (raw)
In-Reply-To: <20140228174920.GF21275@nuc-i3427.alporthouse.com>

On Fri, Feb 28, 2014 at 05:49:20PM +0000, Chris Wilson wrote:
> On Fri, Feb 28, 2014 at 05:37:39PM +0000, Damien Lespiau wrote:
> > On Fri, Feb 28, 2014 at 05:30:02PM +0000, Chris Wilson wrote:
> > > On Fri, Feb 28, 2014 at 04:42:15PM +0000, Damien Lespiau wrote:
> > > > In the future, we need to be able to specify per-pipe number of
> > > > planes/sprites. Let's start today!
> > > 
> > > But today, what's wrong with:
> > > for_each_pipe(pipe) info->num_sprites[pipe] = IS_VLV(dev) ? 2 : 1;
> > 
> > I'd rather have info->num_sprites[pipe] == 0 when the device doesn't
> > support that pipe, even if that value shouldn't be used anywhere.
> 
> for (; pipe < I915_NUM_PIPES; pipe++) info->num_sprites[pipe] = 0;

It should be zero initialized anyway, so we shouldn't need to do that.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-02-28 18:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 16:42 [PATCH 0/3] Make num_sprites a per pipe value (v2) Damien Lespiau
2014-02-28 16:42 ` [PATCH 1/3] drm/i915: Use a pipe variable to cycle trough the pipes Damien Lespiau
2014-02-28 17:25   ` Chris Wilson
2014-02-28 16:42 ` [PATCH 2/3] drm/i915: Add a for_each_sprite() macro Damien Lespiau
2014-02-28 17:26   ` Chris Wilson
2014-02-28 16:42 ` [PATCH 3/3] drm/i915: Make num_sprites a per-pipe value Damien Lespiau
2014-02-28 17:30   ` Chris Wilson
2014-02-28 17:37     ` Damien Lespiau
2014-02-28 17:49       ` Chris Wilson
2014-02-28 18:15         ` Ville Syrjälä [this message]
2014-03-03 14:49         ` Damien Lespiau
2014-03-03 15:01           ` Chris Wilson
2014-03-03  2:24   ` Zhenyu Wang

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=20140228181538.GT3852@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=damien.lespiau@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 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.