Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: linux-samsung-soc@vger.kernel.org
Cc: gustavo.padovan@collabora.co.uk, jy0922.shim@samsung.com,
	inki.dae@samsung.com
Subject: drm/exynos: mixer blending and layer order
Date: Thu, 23 Apr 2015 14:28:59 +0200	[thread overview]
Message-ID: <f71d728970bc036fdce8934a499aba9f@math.uni-bielefeld.de> (raw)

Hello,

I've noticed some inconsistency in what is currently exported as 'zpos' 
DRM propery to userspace. Currently we create three planes, where the 
zpos maps to the mixer 'win' (is this simply short for window?).

But this is wrong since the mixer layer configuration is currently done 
in this way (in mixer_win_reset()):
layer1 (win[1]) > layer0 (win[0]) > video (win[2])

So layer1 is at the top of our stack, and the video layer is at the 
bottom. So regardless on how you interpret the zpos property (0 being 
the top, or 0 being bottom), it doesn't give you accurate information on 
how the planes are ordered.

Related to this is the issue of how to blend planes. When should 
blending of layer be enabled? We probably want to based this on three 
states:
- which layer are enabled
- which pixelformats are associated to the layers
- in which order are the layers (*)

(*) So in the case of 'layer1 > layer0 > video', layer1 disabled, 
layer0/video enabled, layer0 having alpha-pixelformat, we want to blend 
layer0 and the video layer (so effectively making layer0 translucent).

I'm trying to come up with a proposition for that issue in the next 
days, but it would really help to hear thoughts of you guys.

With best wishes,
Tobias

             reply	other threads:[~2015-04-23 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 12:28 Tobias Jakobi [this message]
2015-04-24  2:13 ` drm/exynos: mixer blending and layer order Joonyoung Shim
2015-04-24  8:29   ` Tobias Jakobi
2015-04-27  6:52     ` Joonyoung Shim
2015-04-28 12:58       ` Tobias Jakobi
2015-04-29  6:49         ` Joonyoung Shim
2015-04-29 13:13           ` Tobias Jakobi
2015-04-30  7:17             ` Joonyoung Shim

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=f71d728970bc036fdce8934a499aba9f@math.uni-bielefeld.de \
    --to=tjakobi@math.uni-bielefeld.de \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=inki.dae@samsung.com \
    --cc=jy0922.shim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.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