Hi Tobias, On 04/23/2015 09:28 PM, Tobias Jakobi wrote: > 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. >
I know, actually here zpos doesn't mean order priority of layer, it is just real hardware layer. Exynos mixer has 3 hardware layer, graphic0 layer, graphic1 layer and video layer, so zpos 0 means graphic0 layer, zpos 1 means graphic1 layer, zpos 2 means video layer. Thanks. > Related to this is the issue of how to blend planes. When should blending of > layer be enabled? Current mixer codes permit blending about all layers except bottom layer (just above background layer). > We probably want to based this on three states: > - which layer are enabled > - which pixelformats are associated to the layers This idea is ok but as i said, there is blending issue of background layer. > - in which order are the layers (*) Now we don't permit to change order priority of layer. > > (*) 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 > > Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
