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>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/7] drm/i915: Fix non-scaled sprites for ILK
Date: Fri, 18 Oct 2013 10:35:30 +0300	[thread overview]
Message-ID: <20131018073530.GJ13047@intel.com> (raw)
In-Reply-To: <20131017205603.GA1958@nuc-i3427.alporthouse.com>

On Thu, Oct 17, 2013 at 09:56:03PM +0100, Chris Wilson wrote:
> On Thu, Oct 17, 2013 at 10:53:14PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > For some reason we're enabling sprite scaling on ILK always. That
> > doesn't work well with the new watermark code that expects to use
> > LP1 watermarks with unscaled sprites.
> > 
> > Only enable sprite scaling on ILK when actually needed, just like
> > we do on SNB.
> 
> The sprite plane simply didn't work on my ilk machine unless I
> enabled the scaler. If you want to revert it, at least mention which
> patch you are reverting with justification/demonstration that it works
> now.

Hmm. Oh I see it actually does work when the scaler is enabled. I'm
going to assume the hardware automagically disables LP1+ watermarks in
that case or something, and then it just happens to work even though we
don't set up the watermarks correctly. Earlier I was trying with a >1k
wide 32bpp source w/o scaling, so it exceeded the scaler limits
(width_bytes > 4096) but since the code that does the check didn't
realize scaling was actually enabled it let it through and the
hardware didn't like that very much.

So since it kind of works currently with smaller source widths, I'm
going to leave it alone until I send out the watermark changes. And
I'll pimp up the commit message at that point.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-10-18  7:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 19:53 [PATCH 0/7] drm/i915: Atomic sprites ville.syrjala
2013-10-17 19:53 ` [PATCH 1/7] drm/i915: Don't disable primary when color keying is used ville.syrjala
2013-12-12 20:56   ` Jesse Barnes
2013-12-12 20:58     ` Daniel Vetter
2013-12-13  8:41       ` Ville Syrjälä
2013-10-17 19:53 ` [PATCH 2/7] drm/i915: Fix non-scaled sprites for ILK ville.syrjala
2013-10-17 20:56   ` Chris Wilson
2013-10-18  7:35     ` Ville Syrjälä [this message]
2013-10-17 19:53 ` [PATCH 3/7] drm/i915: Add i915_get_crtc_scanline() ville.syrjala
2013-12-12 20:59   ` Jesse Barnes
2013-10-17 19:53 ` [PATCH 4/7] drm/i915: Shuffle sprite register writes into a tighter group ville.syrjala
2013-12-12 21:00   ` Jesse Barnes
2013-10-17 19:53 ` [PATCH 5/7] drm/i915: Make sprite updates atomic ville.syrjala
2013-12-12 21:04   ` Jesse Barnes
2013-12-12 21:09   ` Jesse Barnes
2013-10-17 19:53 ` [PATCH 6/7] drm/i915: Perform primary enable/disable atomically with sprite updates ville.syrjala
2013-12-12 21:06   ` Jesse Barnes
2013-10-17 19:53 ` [PATCH 7/7] drm/i915: Add pipe update trace points ville.syrjala
2013-12-12 21:08   ` Jesse Barnes
2013-12-13  8:47     ` Ville Syrjälä

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=20131018073530.GJ13047@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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 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.