From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, chaitanya.kumar.borah@intel.com,
Naveen Kumar <naveen1.kumar@intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Subject: Re: [PATCH v6 0/3] Expose modifiers/formats supported by async flips
Date: Thu, 20 Feb 2025 00:33:06 +0200 [thread overview]
Message-ID: <Z7ZcIs22xv3LGr5M@intel.com> (raw)
In-Reply-To: <20250219-asyn-v6-0-b959e6becb3c@intel.com>
On Wed, Feb 19, 2025 at 02:47:22PM +0530, Arun R Murthy wrote:
> All of the formats/modifiers supported by the plane during synchronous
> flips are nor supported by asynchronous flips. The formats/modifiers
> exposed to user by IN_FORMATS exposes all formats/modifiers supported by
> plane and this list varies for async flips. If the async flip supported
> formats/modifiers are exposed to the user, user based on this list can
> take decision to proceed or not and avoid flip failures during async
> flips.
> Discussion around this can be located @
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29618#note_2487123
> Userspace implementation for IN_FORMARTS_ASYNC under review @
> https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4063
FYI I just cooked up support for xorg/modesetting:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1816
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-02-19 22:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 9:17 [PATCH v6 0/3] Expose modifiers/formats supported by async flips Arun R Murthy
2025-02-19 9:17 ` [PATCH v6 1/3] drm/plane: Add new plane property IN_FORMATS_ASYNC Arun R Murthy
2025-02-19 18:54 ` Ville Syrjälä
2025-02-19 9:17 ` [PATCH v6 2/3] drm/plane: modify create_in_formats to accommodate async Arun R Murthy
2025-02-19 18:53 ` Ville Syrjälä
2025-03-12 5:48 ` Borah, Chaitanya Kumar
2025-03-12 5:51 ` Borah, Chaitanya Kumar
2025-02-19 9:17 ` [PATCH v6 3/3] drm/i915/display: Add i915 hook for format_mod_supported_async Arun R Murthy
2025-02-19 19:08 ` Ville Syrjälä
2025-02-19 9:39 ` ✓ CI.Patch_applied: success for Expose modifiers/formats supported by async flips (rev7) Patchwork
2025-02-19 9:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-19 9:41 ` ✓ CI.KUnit: success " Patchwork
2025-02-19 9:57 ` ✓ CI.Build: " Patchwork
2025-02-19 10:00 ` ✓ CI.Hooks: " Patchwork
2025-02-19 10:01 ` ✗ CI.checksparse: warning " Patchwork
2025-02-19 13:53 ` [PATCH v6 0/3] Expose modifiers/formats supported by async flips Simona Vetter
2025-02-19 22:33 ` Ville Syrjälä [this message]
2025-02-20 6:20 ` ✓ CI.Patch_applied: success for Expose modifiers/formats supported by async flips (rev8) Patchwork
2025-02-20 6:20 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-20 6:21 ` ✓ CI.KUnit: success " Patchwork
2025-02-20 6:38 ` ✓ CI.Build: " Patchwork
2025-02-20 6:40 ` ✓ CI.Hooks: " Patchwork
2025-02-20 6:50 ` ✗ CI.checksparse: warning " Patchwork
2025-02-20 7:15 ` ✗ Xe.CI.Full: failure for Expose modifiers/formats supported by async flips (rev7) Patchwork
2025-02-20 7:15 ` ✓ Xe.CI.BAT: success for Expose modifiers/formats supported by async flips (rev8) Patchwork
2025-02-21 0:55 ` ✗ Xe.CI.Full: failure " Patchwork
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=Z7ZcIs22xv3LGr5M@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=naveen1.kumar@intel.com \
--cc=sebastian.brzezinka@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).