Hey Joonyoung,
On 2015-04-29 08:49, Joonyoung Shim wrote:
Without zpos, user may select hw layer only via plane resources order
on
latest exynos drm driver, but zpos can give obvious information to
user.
Of course we can improve zpos property or remove it or as you said
change meaning for layer priority for better usage, but i just say what
current codes mean.
Ok, I think I have some good idea how to properly fix this, but I guess
I should wait for Gustavos's plane cleanup to happen.
I mean it can be invalidated when the layer has any above layers. To
enable blending of layer can do regardless of opaque of behind layer,
right? Please fix me if i misunderstand.
The plan is the following:
- For the bottom-most (enabled) layer we always disable any kind of
blending. We can make this more generic if we should expose
configuration of the background layer to userspace (but this is for the
future).
- For all other (enabled) layers we setup blending depending on the
pixelformat. If it's an alpha format, we enable blending, if not,
disable blending.
Does this sound correct?
Something we can keep in mind for the future:
Attach a 'global alpha' DRM property to each plane so that we can setup
blending even for non-alpha pixelformats. Range would be -1 to 0xff,
where -1 would mean 'disable global-alpha. This would expose the
MXR_GRP_CFG_WIN_BLEND_EN functionality.
I already said it's ok to decide blending feature on/off of layer by
pixel format.
Sorry, I misunderstood you there!
Also, maybe you can help me with this. The SoCs with no video processor
(so 'is_vp_enabled=0'), how many layers does the mixer support there? Is
it just one layer less (so no video layer), or is the video layer
replaced by a normal non-video layer? The current code implies that
there is one layer less, but I want to make sure I get this right! :)
With best wishes,
Tobias
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
