All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 10/10] drm/i915: Support variable cursor height on ivb+
Date: Wed, 8 Mar 2017 11:00:13 +0000	[thread overview]
Message-ID: <20170308110013.GH25284@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20170308104053.GB31595@intel.com>

On Wed, Mar 08, 2017 at 12:40:53PM +0200, Ville Syrjälä wrote:
> On Tue, Mar 07, 2017 at 10:32:14PM +0000, Chris Wilson wrote:
> > On Tue, Mar 07, 2017 at 05:27:09PM +0200, ville.syrjala@linux.intel.com wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > 
> > > IVB introduced the CUR_FBC_CTL register which allows reducing the cursor
> > > height down to 8 lines from the otherwise square cursor dimensions.
> > > Implement support for it. CUR_FBC_CTL can't be used when the cursor
> > > is rotated.
> > > 
> > > Commandeer the otherwise unused cursor->cursor.size to track the
> > > current value of CUR_FBC_CTL to optimize away redundant CUR_FBC_CTL
> > > writes, and to notice when we need to arm the update via CURBASE if
> > > just CUR_FBC_CTL changes.
> > 
> > For userspace to discover this, they should just use trial and error
> > during startup (using the legacy SetCursor)? Though the easiest way
> > would cause the cursor to flicker - just hope the cursor is
> > off/invisible on startup.
> 
> I don't have any decent answer for how to discover this feature. Atomic
> would allow the trial and error approach without flickers. Otherwise I
> guess one could defer the check until the cursor size actually changes.
> Although maybe that won't really work for Xorg. ISTR it wants to know
> things about the cursor size upfront?

We resize the cursor on the fly, so we could do a trial-and-error after
a resize. But yes, the old cursor code used a static one-size fits all.

(gem bo alloc is signalsafe, but malloc isn't -- so we just need to make
sure we have a spare slot to create a new cursor in.)
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-08 11:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 15:26 [PATCH 00/10] drm/i915: Cursor code cleanup and cursor "FBC" support for IVB+ ville.syrjala
2017-03-07 15:27 ` [PATCH 01/10] drm/i915: Parametrize cursor/primary pipe select bits ville.syrjala
2017-03-07 21:51   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 02/10] drm/i915: Pass intel_plane and intel_crtc to plane hooks ville.syrjala
2017-03-07 21:50   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 03/10] drm/i915: Refactor CURBASE calculation ville.syrjala
2017-03-07 21:56   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 04/10] drm/i915: Clean up cursor junk from intel_crtc ville.syrjala
2017-03-07 22:33   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 05/10] drm/i915: Refactor CURPOS calculation ville.syrjala
2017-03-07 21:49   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 06/10] drm/i915: Move cursor position and base handling into the platform specific functions ville.syrjala
2017-03-07 22:35   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 07/10] drm/i915: Drop useless posting reads from cursor commit ville.syrjala
2017-03-07 22:00   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 08/10] drm/i915: Split cursor check_plane into i845 and i9xx variants ville.syrjala
2017-03-07 22:24   ` Chris Wilson
2017-03-08 10:52     ` Ville Syrjälä
2017-03-07 15:27 ` [PATCH 09/10] drm/i915: Use fb->pitches[0] in cursor code ville.syrjala
2017-03-07 22:25   ` Chris Wilson
2017-03-07 15:27 ` [PATCH 10/10] drm/i915: Support variable cursor height on ivb+ ville.syrjala
2017-03-07 22:32   ` Chris Wilson
2017-03-08 10:40     ` Ville Syrjälä
2017-03-08 11:00       ` Chris Wilson [this message]
2017-03-08 10:45     ` Daniel Vetter
2017-03-07 16:18 ` ✓ Fi.CI.BAT: success for drm/i915: Cursor code cleanup and cursor "FBC" support for IVB+ Patchwork

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=20170308110013.GH25284@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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 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.