From: Eric Anholt <eric@anholt.net>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Stefan Schake" <stschake@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
linux-rpi-kernel@lists.infradead.org,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/vc4: Ignore alpha on primary plane
Date: Fri, 02 Mar 2018 09:13:14 -0800 [thread overview]
Message-ID: <87371i8kph.fsf@anholt.net> (raw)
In-Reply-To: <20180302152117.GN5453@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1488 bytes --]
Ville Syrjälä <ville.syrjala@linux.intel.com> writes:
> On Fri, Mar 02, 2018 at 04:06:58PM +0100, Stefan Schake wrote:
>> Hey Ville,
>>
>> On Fri, Mar 2, 2018 at 3:43 PM, Ville Syrjälä
>> <ville.syrjala@linux.intel.com> wrote:
>> > On Fri, Mar 02, 2018 at 04:39:22PM +0200, Ville Syrjälä wrote:
>> >> If you want the plane to always be opaque you shouldn't expose any
>> >> formats with alpha.
>> >>
>> >> Also what happens if one disables the primary plane? Or does the driver
>> >> not allow that?
>> >
>> > Or just makes the plane not cover the entire screen?
>>
>> We've exposed alpha formats in the past so disabling that now would break
>> userspace, certainly Android that chooses alpha-everything.
>
> So it refuses to even run on hardware that can't do per-pixel alpha on
> the primary plane?
>
>> The VC4 HVS
>> has no fixed planes so I'll acknowledge that the concept of a primary plane
>> is somewhat dubious and userspace could disable it or make it not cover the
>> entire screen, making this ineffective.
>>
>> But then ultimately there doesn't seem to be a standard for what the display
>> is supposed to be if you have transparent pixels with no plane to blend to
>> below.
>
> The standard is black. IMO it's a driver bug if it fails to do that.
If the plane is premultiplied (isn't that what DRM planes are supposed
to be? I can't find any docs), then blending against black is the same
as not doing any blending at all.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 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:[~2018-03-02 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 0:32 [PATCH] drm/vc4: Ignore alpha on primary plane Stefan Schake
2018-03-02 14:39 ` Ville Syrjälä
2018-03-02 14:43 ` Ville Syrjälä
2018-03-02 15:06 ` Stefan Schake
2018-03-02 15:21 ` Ville Syrjälä
2018-03-02 15:48 ` Stefan Schake
2018-03-02 16:04 ` Ville Syrjälä
2018-03-02 17:13 ` Eric Anholt [this message]
2018-03-02 17:58 ` Ville Syrjälä
2018-03-05 21:15 ` Eric Anholt
2018-03-06 1:55 ` Stefan Schake
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=87371i8kph.fsf@anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stschake@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox