From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jyri Sarha <jsarha@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 09/15] drm: tilcdc: Replace drm_fb_get_bpp_depth() with drm_format_plane_cpp()
Date: Fri, 10 Jun 2016 15:26:30 +0300 [thread overview]
Message-ID: <575AB1F6.4040805@ti.com> (raw)
In-Reply-To: <20160610122310.GJ4329@intel.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1384 bytes --]
On 10/06/16 15:23, Ville Syrjälä wrote:
> On Fri, Jun 10, 2016 at 03:08:18PM +0300, Tomi Valkeinen wrote:
>> On 10/06/16 15:05, Ville Syrjälä wrote:
>>
>>>> I'm not sure what's the common way, but tilcdc doesn't support alpha.
>>>> ARGB works, of course, by ignoring A, but... If an userspace app creates
>>>> ARGB buffer, does the app expect alpha to work?
>>>
>>> I think what we decided a while ago (at least for i915, but would be good
>>> to use the same convention everywhere) was that ARGB will be assumed to be
>>> pre-multiplied and will enable blending using 1.0*sc+(1.0-sa)*dc as the
>>> function. There have been some efforts at defining some new properties to
>>> control the blend equation, but I guess those got bogged down again.
>>
>> Ok, but that's a bit different topic. The question here is, if the HW
>> doesn't support alpha (no planes, so nothing to blend), should it accept
>> ARGB or not.
>
> What do you mean "no planes"? You have to have a plane if you want
> to scanout a framebuffer. And even if you have just one plane with
> alpha blending, it should be blended with the background color
> (which is black until we get a property to change it).
I mean there's only the crtc with fb. So yes, one plane if you want to
call that a plane. The HW does not support any kind of blending to black
or to anything else.
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-10 12:26 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 23:32 [PATCH v3 00/15] Centralize format information Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 01/15] drm: Move format-related helpers to drm_fourcc.c Laurent Pinchart
2016-06-09 8:36 ` Daniel Vetter
2016-06-09 9:54 ` [PATCH v3.1 " Laurent Pinchart
2016-06-09 10:03 ` Daniel Vetter
2016-06-08 23:32 ` [PATCH v3 02/15] drm: Centralize format information Laurent Pinchart
2016-06-09 8:52 ` Daniel Vetter
2016-06-09 12:23 ` Ville Syrjälä
2016-06-09 12:40 ` Daniel Vetter
2016-06-09 13:05 ` Ville Syrjälä
2016-06-09 13:29 ` Daniel Vetter
2016-06-09 14:13 ` Ville Syrjälä
2016-09-08 13:49 ` Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 03/15] drm: Implement the drm_format_*() helpers as drm_format_info() wrappers Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 04/15] drm: Use drm_format_info() in DRM core code Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 05/15] drm: WARN when calling drm_format_info() for an unsupported format Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 06/15] drm: msm: Replace drm_fb_get_bpp_depth() with drm_format_plane_cpp() Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 07/15] drm: sti: " Laurent Pinchart
2016-06-09 7:52 ` Vincent ABRIOU
2016-06-09 9:17 ` Laurent Pinchart
2016-06-09 12:10 ` Vincent ABRIOU
2016-06-08 23:32 ` [PATCH v3 08/15] drm: hdlcd: " Laurent Pinchart
2016-06-09 9:01 ` Liviu Dudau
2016-07-25 11:10 ` Liviu Dudau
2016-09-08 14:45 ` Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 09/15] drm: tilcdc: " Laurent Pinchart
2016-06-10 11:51 ` Tomi Valkeinen
2016-06-10 12:05 ` Ville Syrjälä
2016-06-10 12:08 ` Tomi Valkeinen
2016-06-10 12:23 ` Ville Syrjälä
2016-06-10 12:26 ` Tomi Valkeinen [this message]
2016-06-10 12:29 ` Ville Syrjälä
2016-06-10 12:48 ` Tomi Valkeinen
2016-06-10 13:08 ` Tomi Valkeinen
2016-06-10 13:16 ` Jyri Sarha
2016-06-10 13:25 ` Ville Syrjälä
2016-06-10 14:21 ` Daniel Vetter
2016-06-10 12:07 ` Laurent Pinchart
2016-06-10 12:08 ` [PATCH v3.1 " Laurent Pinchart
2016-06-10 12:21 ` Tomi Valkeinen
2016-06-08 23:32 ` [PATCH v3 10/15] drm: cirrus: " Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 11/15] drm: gma500: Replace drm_fb_get_bpp_depth() with drm_format_info() Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 12/15] drm: amdgpu: Replace drm_fb_get_bpp_depth() with drm_format_plane_cpp() Laurent Pinchart
2016-06-09 1:42 ` Michel Dänzer
2016-06-09 9:18 ` Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 13/15] drm: radeon: " Laurent Pinchart
2016-06-08 23:32 ` [PATCH v3 14/15] drm: vmwgfx: Replace drm_fb_get_bpp_depth() with drm_format_info() Laurent Pinchart
2016-06-27 17:51 ` Sinclair Yeh
2016-06-08 23:32 ` [PATCH v3 15/15] drm: Don't export the drm_fb_get_bpp_depth() function Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2016-06-08 23:30 [PATCH v3 00/15] Centralize format information Laurent Pinchart
2016-06-08 23:31 ` [PATCH v3 09/15] drm: tilcdc: Replace drm_fb_get_bpp_depth() with drm_format_plane_cpp() Laurent Pinchart
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=575AB1F6.4040805@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.