From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
"xaver.hugl@kde.org" <xaver.hugl@kde.org>,
"andrealmeid@igalia.com" <andrealmeid@igalia.com>,
"Kumar, Naveen1" <naveen1.kumar@intel.com>,
"Syrjala, Ville" <ville.syrjala@intel.com>,
Dmitry Baryshkov <lumag@kernel.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH [RFC] v3 5/7] drm/atomic: Allow planes with NULL fb along with async flip
Date: Fri, 9 Jan 2026 12:23:00 +0100 [thread overview]
Message-ID: <05ac3e30-b3dc-48ea-96db-1cbdb4454730@mailbox.org> (raw)
In-Reply-To: <IA0PR11MB73076D91D60F168B9D112051BA82A@IA0PR11MB7307.namprd11.prod.outlook.com>
On 1/9/26 12:08, Murthy, Arun R wrote:
>> From: Michel Dänzer <michel.daenzer@mailbox.org>
>> 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
Can't see any such request there. I suspect there might be a misunderstanding.
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
next prev parent reply other threads:[~2026-01-09 11:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 9:43 [PATCH RFC v3 0/7] Async Flip in Atomic ioctl corrections Arun R Murthy
2026-01-08 9:43 ` [PATCH [RFC] v3 1/7] drm/atomic/plane: Add plane property for async flip Arun R Murthy
2026-01-08 9:43 ` [PATCH [RFC] v3 2/7] drm/atomic/plane: create async flip property for plane Arun R Murthy
2026-01-08 9:43 ` [PATCH [RFC] v3 3/7] drm/atomic: Re-route the async flip based on the flag Arun R Murthy
2026-01-08 9:43 ` [PATCH [RFC] v3 4/7] drm/atomic: Move the plane property check for async flip to atomic_check Arun R Murthy
2026-01-08 9:43 ` [PATCH [RFC] v3 5/7] drm/atomic: Allow planes with NULL fb along with async flip Arun R Murthy
2026-01-09 9:43 ` Michel Dänzer
2026-01-09 11:08 ` Murthy, Arun R
2026-01-09 11:23 ` Michel Dänzer [this message]
2026-01-12 8:26 ` Murthy, Arun R
2026-01-12 11:24 ` Michel Dänzer
2026-01-12 15:20 ` Murthy, Arun R
2026-01-12 15:25 ` Michel Dänzer
2026-01-12 16:03 ` Xaver Hugl
2026-01-13 2:47 ` Murthy, Arun R
2026-01-08 9:43 ` [PATCH [RFC] v3 6/7] drm/atomic: flip_done signal for planes Arun R Murthy
2026-01-08 9:43 ` [PATCH [RFC] v3 7/7] drm/i915/irq: Enable flip_done for each plane on async flip Arun R Murthy
2026-01-08 9:53 ` ✓ CI.KUnit: success for " Patchwork
2026-01-08 10:35 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-08 13:09 ` ✓ Xe.CI.Full: " Patchwork
2026-01-09 9:43 ` [PATCH RFC v3 0/7] Async Flip in Atomic ioctl corrections Michel Dänzer
2026-01-09 11:07 ` Murthy, Arun R
2026-01-09 11:22 ` Michel Dänzer
2026-01-12 8:23 ` Murthy, Arun R
2026-01-12 11:34 ` Michel Dänzer
2026-01-12 15:35 ` Murthy, Arun R
2026-02-11 5:48 ` Murthy, Arun R
2026-02-11 8:57 ` Michel Dänzer
2026-02-11 13:38 ` Murthy, Arun R
2026-02-11 13:51 ` Michel Dänzer
2026-02-11 13:58 ` Murthy, Arun R
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=05ac3e30-b3dc-48ea-96db-1cbdb4454730@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=airlied@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=naveen1.kumar@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@intel.com \
--cc=xaver.hugl@kde.org \
/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