> As I commented earlier in the gitlab issue [1], any change of property,
> including disabling a plane is not allowed in the async commit.
> We must disable a plane (e.g. HW cursor) during the first (synchronized)
> flip, and allowing later flips to proceed asynchronously.
> This change should b
On 05-08-2025 03:02, Xaver Hugl wrote:
Am Mo., 4. Aug. 2025 um 11:54 Uhr schrieb Murthy, Arun R
:
On 01-08-2025 18:40, Xaver Hugl wrote:
It's entirely valid and correct for compositors to include disabled
planes in the atomic commit, and doing that should not prevent async
flips from working. T
redhat.com; intel-
>g...@lists.freedesktop.org; amd-...@lists.freedesktop.org;
>alexdeuc...@gmail.com
>Subject: Re: [PATCH v3] drm: don't run atomic_async_check for disabled planes
>
>Am Mo., 4. Aug. 2025 um 11:54 Uhr schrieb Murthy, Arun R
>:
>>
>> On 01-08-2025 18:40, Xaver Hugl wro
Am Mo., 4. Aug. 2025 um 11:54 Uhr schrieb Murthy, Arun R
:
>
> On 01-08-2025 18:40, Xaver Hugl wrote:
> > It's entirely valid and correct for compositors to include disabled
> > planes in the atomic commit, and doing that should not prevent async
> > flips from working. To fix that, this commit mov
On 01-08-2025 18:40, Xaver Hugl wrote:
It's entirely valid and correct for compositors to include disabled
planes in the atomic commit, and doing that should not prevent async
flips from working. To fix that, this commit moves the plane check
to after all the properties of the object have been se
It's entirely valid and correct for compositors to include disabled
planes in the atomic commit, and doing that should not prevent async
flips from working. To fix that, this commit moves the plane check
to after all the properties of the object have been set, and skips
the async checks if the plan
