dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Connolly <caleb@connolly.tech>
To: dri-devel@vger.kernel.org
Cc: martijn@brixit.nl, dri-devel@lists.freedesktop.org,
Subject: Display notch support
Date: Tue, 27 Apr 2021 20:47:21 +0000	[thread overview]
Message-ID: <f8747f99-0695-5be0-841f-4f72ba5d5da3@connolly.tech> (raw)

With many more non-desktop form factor devices landing in the kernel, 
we're starting to run up against some limitations. Notably devices with 
display notches, cutouts and rounded corners.

Given that the DRI subsystem already deals with physical display 
properties like panel orientation which is fixed in device tree, it 
would make sense to also define other properties like parts of the 
display which are obscured there too. This can then be read by desktop 
environments and UI elements can be suitably adjusted.

Android already deals with non-square displays, however they also keep 
the device configuration in userspace: 

A solution to make this configuration generic and exposed by the kernel 
would standardise this across Linux and potentially Android too which 
would be extremely beneficial to the mobile Linux community at large.

Does this seem like a feasible solution to solving the notch problem and 
avoiding a situation where every compositor have their own method of 
describing cutouts and rounded corners?



dri-devel mailing list

             reply	other threads:[~2021-04-27 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 20:47 Caleb Connolly [this message]
2021-04-28  7:21 ` Display notch support 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

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=f8747f99-0695-5be0-841f-4f72ba5d5da3@connolly.tech \
    --to=caleb@connolly.tech \
    --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).