[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Bi9El_nuZXA997YlVyCzD5s7KfP820IVUuYiB69mgXnjQbfCgOucCBe6aKvSFrMzB_9DwxO2lli_MqLzMuGZ-rmrRp57vePsTwUarEweLJs=@emersion.fr>
Date: Mon, 23 Oct 2023 08:27:17 +0000
From: Simon Ser <contact@...rsion.fr>
To: Michel Dänzer <michel.daenzer@...lbox.org>
Cc: André Almeida <andrealmeid@...lia.com>,
pierre-eric.pelloux-prayer@....com,
'Marek Olšák' <maraeo@...il.com>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org, amd-gfx@...ts.freedesktop.org,
Pekka Paalanen <ppaalanen@...il.com>,
dri-devel@...ts.freedesktop.org, kernel-dev@...lia.com,
alexander.deucher@....com, hwentlan@....com,
christian.koenig@....com, joshua@...ggi.es
Subject: Re: [PATCH v7 4/6] drm: Refuse to async flip with atomic prop changes
On Sunday, October 22nd, 2023 at 12:12, Michel Dänzer <michel.daenzer@...lbox.org> wrote:
> On 10/17/23 14:16, Simon Ser wrote:
>
> > After discussing with André it seems like we missed a plane type check
> > here. We need to make sure FB_ID changes are only allowed on primary
> > planes.
>
> Can you elaborate why that's needed?
Current drivers are in general not prepared to perform async page-flips
on planes other than primary. For instance I don't think i915 has logic
to perform async page-flip on an overlay plane FB_ID change.
Powered by blists - more mailing lists