dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Connolly <caleb@connolly.tech>
To: Simon Ser <contact@emersion.fr>
Cc: martijn@brixit.nl, dri-devel@lists.freedesktop.org,
	dri-devel@vger.kernel.org, ~postmarketos/upstreaming@lists.sr.ht
Subject: Re: Display notch support
Date: Mon, 03 May 2021 12:13:36 +0000	[thread overview]
Message-ID: <c0cdabab-74b6-b2e6-4a4d-edd737d5ae6a@connolly.tech> (raw)
In-Reply-To: <ck2MR5NpcE5l0NZuJnX7O7DLXBGxiFr_1LCqlDlsC0GNC3PEtTEcx1-vfIp8ZLyMhfxmv4_MyGaYBjZBawdTaWzButF0qkbdc-9EYhVFZYk=@emersion.fr>

On 28/04/2021 8:21 am, Simon Ser 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 [1] 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.
> [1]: https://developer.android.com/reference/android/view/DisplayCutout

It looks like rounded corners only get a developer facing API in Android 
12 [1].

However from a vendor perspective it's possible to set padding for 
rounded corners [2], although this seems to mostly be a hack.

It seems like it would make sense to deal with cutouts and rounded 
corners separately, cutouts are always convex where rounded corners are 
always concave, they have different implications on how content should 
be adjusted.



dri-devel mailing list

      parent reply	other threads:[~2021-05-03 12:13 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
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 [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c0cdabab-74b6-b2e6-4a4d-edd737d5ae6a@connolly.tech \
    --to=caleb@connolly.tech \
    --cc=contact@emersion.fr \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dri-devel@vger.kernel.org \
    --cc=martijn@brixit.nl \
    --cc=~postmarketos/upstreaming@lists.sr.ht \


* 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).