From: "Wentland, Harry" <Harry.Wentland@amd.com>
To: "Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane_alpha_blend: Paint FBs with cairo source operator
Date: Wed, 27 Feb 2019 19:49:19 +0000 [thread overview]
Message-ID: <dcee29cd-790f-1bdc-e676-ba984c877770@amd.com> (raw)
In-Reply-To: <22ecbaf2-de10-d2e2-86e5-9d93200b2ea8@amd.com>
snip
>>
>>>
>>> However, this patch would still be needed since the fill will still be
>>> blended by default. When creating transparent or semi-transparent
>>> buffers they should be filled in with the cairo source operator or the
>>> alpha channel won't be set to the correct value.
>>
>> AFAICS if the dest alpha and color are both 0.0 the only fb that is
>> wrong is argb_fb_0 since the current code will in fact give us
>> alpha of 1.0. draw_squares() with OVER should still give us the
>> same results as we'd get with SOURCE.
>>
>> I guess this means any test which is currently using argb_fb_0
>> is definitely not testing per-pixel alpha.
>>
>> So argb_transparant() and basic_alpha() are simply useless atm?
>>
>> constant_alpha_min() sets pixel_blend_mode to None anyway so
>> doesn't really matter what we have in the alpha channel.
>>
>> Not sure why those tests aren't doing the gray_fb thing the other tests
>> are using...
>>
>> Anyways, no point in blending when you don't have to so
>> the patch seems to make sense to me either way:
>> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Thanks for the review. Like you said, the main problem is with argb_fb_0
> and argb_transparent and basic_alpha but it's better to be explicit
> about intent with the square filling too IMO.
>
Merged.
> Nicholas Kazlauskas
>
snip
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-27 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 17:08 [igt-dev] [PATCH i-g-t] tests/kms_plane_alpha_blend: Paint FBs with cairo source operator Nicholas Kazlauskas
2019-02-22 17:39 ` Ville Syrjälä
2019-02-22 17:46 ` Kazlauskas, Nicholas
2019-02-22 18:57 ` Ville Syrjälä
2019-02-25 14:32 ` Kazlauskas, Nicholas
2019-02-27 19:49 ` Wentland, Harry [this message]
2019-02-22 18:27 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-02-25 16:47 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_alpha_blend: Paint FBs with cairo source operator (rev2) Patchwork
2019-02-25 23:08 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=dcee29cd-790f-1bdc-e676-ba984c877770@amd.com \
--to=harry.wentland@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox