> -----Original Message----- > From: Michel Dänzer <[email protected]> > Sent: Friday, January 9, 2026 3:14 PM > To: Murthy, Arun R <[email protected]>; Maarten Lankhorst > <[email protected]>; Maxime Ripard <[email protected]>; > Thomas Zimmermann <[email protected]>; David Airlie > <[email protected]>; Simona Vetter <[email protected]>; Jani Nikula > <[email protected]>; Vivi, Rodrigo <[email protected]>; Joonas > Lahtinen <[email protected]>; Tvrtko Ursulin > <[email protected]>; [email protected]; [email protected]; Kumar, > Naveen1 <[email protected]>; Syrjala, Ville <[email protected]>; > Dmitry Baryshkov <[email protected]> > Cc: [email protected]; [email protected]; intel- > [email protected] > Subject: Re: [PATCH [RFC] v3 5/7] drm/atomic: Allow planes with NULL fb along > with async flip > > On 1/8/26 10:43, Arun R Murthy wrote: > > Along with async flip if there is a request to disable a sync plane by > > providing a NULL fb allow them. > > That could result in async changes to other planes taking effect in an earlier > refresh cycle than the sync plane being disabled, couldn't it? In which case > the > commit arguably wouldn't actually be "atomic". > This is the request from the community to allow disabling of a sync plane in an async flip atomic ioctl. https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13834
Thanks and Regards, Arun R Murthy -------------------
