Michel Dänzer 23f3c17f0c kms/impl-device: Use deadline timer for all updates
Not with VRR though, because the deadline timer fires at most every 33ms
then.

Previously, the deadline timer was used only for cursor-only updates.
Using it for other updates means they pick up the latest cursor position
available at the deadline, resulting in the lowest possible input→output
latency for cursor movement.

TTBOMK this unlocks the full potential of the KMS thread given the
current atomic KMS API.

v2:
* Don't call meta_kms_update_merge_from with twice the same update
  pointer.
v3:
* Don't arm deadline timer if crtc_frame->pending_page_flip is true.
v4:
* Tweak want_deadline_timer indentation per check-code-style CI job.
v5:
* Also check crtc_frame->await_flush for want_deadline_timer.
v6:
* Tweak coding style to keep lines shorter. (Jonas Ådahl)

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3964>
2024-12-23 09:29:07 +00:00
..
2024-06-25 20:48:24 +02:00
2023-08-30 08:48:23 +02:00
2023-08-07 22:24:36 +00:00
2023-11-15 10:24:41 +00:00
2023-08-30 08:48:23 +02:00
2023-08-30 08:48:23 +02:00
2023-08-30 08:48:23 +02:00
2023-08-30 08:48:23 +02:00
2023-08-30 08:48:23 +02:00
2024-08-31 01:06:33 +02:00
2023-11-03 11:27:52 +00:00