From: Pekka Paalanen <email@example.com>
To: Simon Ser <firstname.lastname@example.org>
Cc: email@example.com, Caleb Connolly <firstname.lastname@example.org>,
Subject: Re: Display notch support
Date: Wed, 28 Apr 2021 10:44:03 +0300 [thread overview]
Message-ID: <20210428104403.1e49f270@eldfell> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1953 bytes --]
On Wed, 28 Apr 2021 07:21:28 +0000
Simon Ser <email@example.com> wrote:
> > A solution to make this configuration generic and exposed by the kernel
> > would standardise this across Linux
> Having a KMS property for this makes sense to me.
> Chatting with Jani on IRC, it doesn't seem like there's any EDID or
> DisplayID block for this.
> Note, Android exposes a data structure  with:
> - Margin of the cut-out for each edge of the screen
> - One rectangle per edge describing the cut-out region
> - Size of the curved area for each edge of a waterfall display
> I haven't found anything describing the rounded corners of the display.
> : https://developer.android.com/reference/android/view/DisplayCutout
I'm kind of worried whether you can design a description structure that
would be good for a long time. That list already looks quite
complicated. Add also watch-like devices with circular displays.
Would the kernel itself use this information at all?
If not, is there not a policy that DT is not a userspace configuration
You mentioned the panel orientation property, but that is used by the
kernel for fbcon or something, is it not? Maybe as the default value
for the CRTC rotation property which actually turns the image?
Assuming that you succeed in describing these non-usable, funny
(waterfall edge), funny2 (e.g. behind a shade or filter so visible but
not normal), funny3 (e.g. phone button area with maybe tactile
markings), and normal areas, how would userspace handle this
Funny2 and funny3 are hypothetical but maybe not too far-fetched.
Is there any provision for generic userspace to handle this generically?
This seems more like a job for the hypothetical liboutput, just like
recognising HMDs (yes, I know, kernel does that already, but there is a
point that kernel may not want to put fbcon on a HMD).
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
dri-devel mailing list
next prev parent reply other threads:[~2021-04-28 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 20:47 Display notch support Caleb Connolly
2021-04-28 7:21 ` Simon Ser
2021-04-28 7:44 ` Pekka Paalanen [this message]
2021-04-28 7:51 ` Simon Ser
2021-04-28 12:01 ` Daniel Vetter
2021-04-28 12:18 ` Jani Nikula
2021-05-03 12:13 ` Caleb Connolly
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).