All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org,
	Pekka Paalanen <pekka.paalanen@collabora.com>,
	Simona Vetter <simona.vetter@ffwll.ch>
Subject: Re: [PATCH v2] drm/doc: document front-buffer rendering
Date: Tue, 6 May 2025 16:56:20 +0300	[thread overview]
Message-ID: <aBoVBAhk21Dkh5vV@intel.com> (raw)
In-Reply-To: <7fLdC-okfQ3e09zwXInhSeD2aOqmwMIfjKXkBIfKE86bP_Tw3eGwhZj578-18aMD50dM1nv9MtQP-HEIqp_yDwm68RfFng6bNrvR7UTD47k=@emersion.fr>

On Thu, May 01, 2025 at 11:25:11AM +0000, Simon Ser wrote:
> Ah, sorry, I missed this message.
> 
> On Monday, April 14th, 2025 at 15:28, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> 
> > Should probably add a caveat that this needs to be a sync commit/flip.
> > The way the async flip was specified for atomic explicitly requires the
> > driver to ignore the plane when the fb doesn't change.
> 
> I don't believe so. Async flip should work fine with same FB.

The way you specified this means the kernel has to explicitly ignore
it because not all planes may support async flips. We can't generally
mix async and sync stuff into the same commit.

> The kernel
> will only ignore other props if they match their previous value.
> 
> > Also use dirtyfb instead if you don't want to get throttled to the
> > vrefresh rate. Tthough I think with some drivers you might get
> > throttled even with dirtyfb...
> 
> Like Simona, I'm really not a fan of mixing atomic and non-atomic. It's
> caused issues in the past, e.g. ChromeOS forcing amdgpu to reject atomic
> commits which could cause future cursor IOCTLs to fail.

-- 
Ville Syrjälä
Intel

      reply	other threads:[~2025-05-06 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14  8:56 [PATCH v2] drm/doc: document front-buffer rendering Simon Ser
2025-04-14 11:06 ` Pekka Paalanen
2025-04-17 15:19   ` Simon Ser
2025-04-22 11:05     ` Pekka Paalanen
2025-04-30 21:37       ` Simon Ser
2025-04-14 13:28 ` Ville Syrjälä
2025-04-14 14:51   ` Simona Vetter
2025-05-01 11:25   ` Simon Ser
2025-05-06 13:56     ` Ville Syrjälä [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:
  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=aBoVBAhk21Dkh5vV@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=contact@emersion.fr \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=pekka.paalanen@collabora.com \
    --cc=simona.vetter@ffwll.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.