From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Stefan Schake <stschake@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC PATCH hwc] drm_hwcomposer: set CRTC background color when available
Date: Mon, 2 Jul 2018 14:22:09 +0200 [thread overview]
Message-ID: <b6b4c141-a1b3-95a1-35d8-ead65922fbac@linux.intel.com> (raw)
In-Reply-To: <CAOZHkRxXQCFAJuaMdvzhzZc8odagaAuw=4g6_c+prGaL84jHBA@mail.gmail.com>
Op 29-06-18 om 12:27 schreef Stefan Schake:
> Hey Maarten,
>
> On Fri, Jun 29, 2018 at 12:05 PM, Maarten Lankhorst
> <maarten.lankhorst@linux.intel.com> wrote:
>> Op 22-02-18 om 04:54 schreef Stefan Schake:
>>> Android assumes an implicit black background layer is always present
>>> behind all layers it specifies for composition. drm_hwcomposer currently
>>> punts responsibility for this to the kernel/DRM platform and puts layers
>>> with per-pixel alpha content on the primary plane when requested.
>>>
>>> On some platforms (e.g. VC4) a background color fill has a cycle cost for
>>> the hardware composer and is not enabled by default. Instead, userland can
>>> request a background color through a CRTC property. Use this property to
>>> specify the implicit black background Android expects.
>>>
>>> Signed-off-by: Stefan Schake <stschake@gmail.com>
>>> ---
>>> Kernel changes for this (background_color) are available here:
>>>
>>> https://github.com/stschake/linux/commits/background-upstream
>>>
>>> Sending as RFC because I'm not entirely clear on whose responsibility
>>> this should be, on most DRM drivers it seems to be implicit. I think
>>> a case could also be made that VC4 should not accept alpha formats on
>>> the lowest layer or enable background color fill when given one anyway.
>>> On the other hand, userland control over background color seems desirable
>>> regardless and is a feature of multiple hardware composers (i915, vc4, omap).
>> Ping? Would be nice if we were moving forward. :)
> I was unclear if DRM specified a black background when writing this.
> Someone pointed me towards the excerpt in the docs that explicitly
> mandates black background fill and so I ended up writing a VC4 patch
> that automatically sets it when required instead of the optional property
> used here.
>
> Adding a background_color property would still be desirable, but I'm
> unclear on what the userspace would be at the moment. drm_hwc doesn't
> need any background color other than black and since that is the DRM
> default, it wouldn't need to use a property.
>
> Thanks,
> Stefan
It would still be useful for e-paper displays where the background color would be better suited
as white, or when we want to blend a different color than black. But I fear for now there's no
real userspace. :(
Which is unfortunate, because the series are easy to implement, but it's just a case where there's
no need from userspace yet for the hw capability.
~Maarten
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-07-02 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 3:54 [RFC PATCH hwc] drm_hwcomposer: set CRTC background color when available Stefan Schake
2018-02-22 10:04 ` Robert Foss
2018-02-22 12:23 ` Stefan Schake
2018-02-22 20:47 ` Eric Anholt
2018-02-23 14:34 ` Stefan Schake
2018-02-28 10:53 ` Robert Foss
2018-03-02 0:41 ` Stefan Schake
2018-03-02 14:34 ` Robert Foss
2018-03-06 7:46 ` Daniel Vetter
2018-06-29 10:05 ` Maarten Lankhorst
2018-06-29 10:27 ` Stefan Schake
2018-07-02 12:22 ` Maarten Lankhorst [this message]
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=b6b4c141-a1b3-95a1-35d8-ead65922fbac@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stschake@gmail.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