[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190710164622.GA15868@phenom.ffwll.local>
Date: Wed, 10 Jul 2019 18:46:23 +0200
From: Daniel Vetter <daniel@...ll.ch>
To: Rodrigo Siqueira <rodrigosiqueiramelo@...il.com>
Cc: Daniel Vetter <daniel@...ll.ch>,
Haneen Mohammed <hamohammed.sa@...il.com>,
David Airlie <airlied@...ux.ie>,
Simon Ser <contact@...rsion.fr>,
Oleg Vasilev <oleg.vasilev@...el.com>,
Mamta Shukla <mamtashukla555@...il.com>,
Harry Wentland <harry.wentland@....com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] drm/vkms: Use alpha value for blending
On Tue, Jul 09, 2019 at 10:52:02PM -0300, Rodrigo Siqueira wrote:
> The first patch of this series reworks part of the blend function to
> improve the readability and also for preparing it for using alpha value.
> The second patch updates the blend function for applying alpha value for
> a fully transparent blend. After applying this patchset,
> pipe-a-cursor-alpha-transparent in kms_cursor_crc start to pass.
Looking at the series I wonder whether we should go right ahead to
reworking the entire composer pipeline to future proof it for multiple
planes and other pixel modes. Or whether enabling alpha blending with what
we have now is a better idea, but that means more complicated refactoring
later on ...
> This patchset depends on:
> https://patchwork.freedesktop.org/series/61738/
Ok I guess I need to look at this one here first.
-Daniel
>
> Rodrigo Siqueira (2):
> drm/vkms: Rework blend function
> drm/vkms: Use alpha channel for blending cursor with primary
>
> drivers/gpu/drm/vkms/vkms_composer.c | 54 ++++++++++++++++++++--------
> 1 file changed, 39 insertions(+), 15 deletions(-)
>
> --
> 2.21.0
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists