[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79ed136a-cedd-4e97-adb8-bc3f4f2b8bb4@mailbox.org>
Date: Mon, 26 Jan 2026 11:27:00 +0100
From: Michel Dänzer <michel.daenzer@...lbox.org>
To: Christian König <christian.koenig@....com>,
Timur Kristóf <timur.kristof@...il.com>,
Hamza Mahfooz <someguy@...ective-light.com>, dri-devel@...ts.freedesktop.org
Cc: Alex Deucher <alexander.deucher@....com>, David Airlie
<airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Harry Wentland <harry.wentland@....com>, Leo Li <sunpeng.li@....com>,
Rodrigo Siqueira <siqueira@...lia.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
Sunil Khatri <sunil.khatri@....com>, Ce Sun <cesun102@....com>,
Lijo Lazar <lijo.lazar@....com>, Kenneth Feng <kenneth.feng@....com>,
Ivan Lipski <ivan.lipski@....com>, Alex Hung <alex.hung@....com>,
Tom Chung <chiahsuan.chung@....com>, Melissa Wen <mwen@...lia.com>,
Michel Dänzer <mdaenzer@...hat.com>,
Fangzhi Zuo <Jerry.Zuo@....com>, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, Mario Limonciello <mario.limonciello@....com>
Subject: Re: [PATCH 1/2] drm: introduce page_flip_timeout()
On 1/26/26 11:14, Christian König wrote:
> On 1/23/26 15:44, Timur Kristóf wrote:
>> On Friday, January 23, 2026 2:52:44 PM Central European Standard Time
>> Christian König wrote:
>>
>>> So as far as I can see the whole approach doesn't make any sense at all.
>>
>> Actually this approach was proposed as a solution at XDC 2025 in Harry's
>> presentation, "DRM calls driver callback to attempt recovery", see page 9 in
>> this slide deck:
>>
>> https://indico.freedesktop.org/event/10/contributions/431/attachments/
>> 267/355/2025%20XDC%20Hackfest%20Update%20v1.2.pdf
>>
>> If you disagree with Harry, please make a counter-proposal.
>
> Well I must have missed that detail otherwise I would have objected.
>
> But looking at the slide Harry actually pointed out what immediately came to my mind as well, e.g. that the Compositor needs to issue a full modeset to re-program the CRTC.
In principle, the kernel driver has all the information it needs to reprogram the HW by itself. Not sure why the compositor would need to be actively involved.
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
Powered by blists - more mailing lists