mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Joonas Kylmälä" <joonas.kylmala@iki.fi>
To: dri-devel@lists.freedesktop.org,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	"Maxime Ripard" <maxime.ripard@bootlin.com>,
	airlied@linux.ie, linux-kernel <linux-kernel@vger.kernel.org>,
	"Jernej Škrabec" <jernej.skrabec@siol.net>
Cc: linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Preferring cursor plane over overlay plane
Date: Mon, 26 Mar 2018 14:14:00 +0000	[thread overview]
Message-ID: <5edad360-d05d-1bb8-c1f2-925138784fef@iki.fi> (raw)

Hi DRM subsystem developers,

I ran into this patch where overlay plane was switched to cursor plane
because there was no proper cursor plane available on the display
hardware: <https://lkml.org/lkml/2018/3/17/120>. Can we discuss whether
to have a policy of using a normal plane for cursor plane in case a
dedicated HW cursor plane is missing?

Daniel Vetter suggests that it might be fine to use normal plane for
cursor plane because how to use the plane would be only "a hint to
userspace" (see the email linked).

My motivation for having this discussion is that the newer Allwinner
SoCs don't have dedicated HW cursor plane and the sun4i DRM driver
currently uses the extra planes as overlay planes which makes moving the
cursor on Xfce4 DE a terrible experience. To have better cursor moving
experience one overlay plane would need to be sacrificed.

Also, I probably missed some recipients for this email so please forward
it to the recipients you think might be interested about this.

Best regards,
Joonas

             reply	other threads:[~2018-03-26 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 14:14 Joonas Kylmälä [this message]
2018-03-26 14:22 ` [linux-sunxi] " Chen-Yu Tsai
2018-03-26 14:45   ` Maxime Ripard
2018-03-26 15:01     ` Chen-Yu Tsai
2018-03-27  7:07       ` Maxime Ripard

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=5edad360-d05d-1bb8-c1f2-925138784fef@iki.fi \
    --to=joonas.kylmala@iki.fi \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@siol.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®