From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 601F1C433B4 for ; Mon, 3 May 2021 12:13:46 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D22E861185 for ; Mon, 3 May 2021 12:13:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D22E861185 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=connolly.tech Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 18E806E0B9; Mon, 3 May 2021 12:13:45 +0000 (UTC) Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1012C6E8B0 for ; Mon, 3 May 2021 12:13:42 +0000 (UTC) Date: Mon, 03 May 2021 12:13:36 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=connolly.tech; s=protonmail; t=1620044020; bh=/+Uui9Hgpk+QynuM+bEkYRSPZ/IUi3/Z5yoU5LfCVc8=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=Vmg1ohMwqVYlk0tZdMzAe8IX+buDMbWqIHX01AXjUGwMgmz5nb8cPJ9/XWpyGUus7 t/JWDCDw9cMMO7RYv0PCuUI1WH493F+UKgx+wUHg6YkKOhfhjRRx/tzLlOvpPTsV0D 9mZrvZJdhsAc+9cvlLSHwYWtXmwdnWBvlxfFdtVc= To: Simon Ser From: Caleb Connolly Subject: Re: Display notch support Message-ID: In-Reply-To: References: MIME-Version: 1.0 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Caleb Connolly Cc: martijn@brixit.nl, dri-devel@lists.freedesktop.org, dri-devel@vger.kernel.org, ~postmarketos/upstreaming@lists.sr.ht Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" 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. [1]: https://developer.android.com/about/versions/12/features#rounded_corner_apis [2]: https://github.com/LineageOS/android_device_oneplus_enchilada/commit/923c86a13b5ffb58683206a73a0813783e71e3fb _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel