mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Harry Wentland <harry.wentland@amd.com>, linux-kernel@vger.kernel.org
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/plane-helper: Add a drm_plane_helper_atomic_check() helper
Date: Tue, 13 Sep 2022 16:46:31 +0200	[thread overview]
Message-ID: <2b67dfcc-9027-6bb5-d42b-7465f2236747@redhat.com> (raw)
In-Reply-To: <b81591c4-934c-4b70-fbf0-b0f4663a6d1c@amd.com>

On 9/13/22 15:49, Harry Wentland wrote:
> 
> 
> On 2022-09-13 05:33, Javier Martinez Canillas wrote:
>> Provides a default plane state check handler for primary planes that are a
>> fullscreen scanout buffer and whose state scale and position can't change.
>>
> 
> Even though this might be how some drivers are handling the primary
> plane this assumption is not universal. For example, on ChromeOS when
> the (default) underlay strategy is selected the compositor will
> position the video plane as the bottom-most plane and mark it
> as primary, while the desktop plane is marked as overlay and
> will contain an alpha cutout to show the underlying video.
>
> In this case the video plane (primary) won't span the screen
> and is regularly panned and resized.
>

I see. Interesting.

> No objections to this change as it helps share code between drivers,
> but maybe specify that this behavior is a unique requirement of
> these drivers.
> 

I tried to make it clear in the comment by mentioning that this helper
is applicable for drivers whose primary plane is always fullscreen and
can't scale or change position.

Any suggestions of what's missing in the helper kernel-doc comment to be
more clear ?

> Harry
> 

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


  reply	other threads:[~2022-09-13 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  9:33 Javier Martinez Canillas
2022-09-13 13:49 ` Harry Wentland
2022-09-13 14:46   ` Javier Martinez Canillas [this message]
2022-09-13 15:08     ` Harry Wentland
2022-09-13 15:15   ` Thomas Zimmermann

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=2b67dfcc-9027-6bb5-d42b-7465f2236747@redhat.com \
    --to=javierm@redhat.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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

all inboxes | Powered by JetHome®