From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: Xaver Hugl <xaver.hugl@kde.org>
Cc: 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>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>, <harry.wentland@amd.com>,
<uma.shankar@intel.com>, <louis.chauvet@bootlin.com>,
<dri-devel@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v7 1/5] drm: Define user readable error codes for atomic ioctl
Date: Thu, 22 Jan 2026 08:24:03 +0530 [thread overview]
Message-ID: <d481788c-227f-479f-bc2a-7e30d55832bd@intel.com> (raw)
In-Reply-To: <CAFZQkGwdpfEzv=210AQxBhqauj4NmSQCb1m1xfD1+e6rsTrwow@mail.gmail.com>
On 21-01-2026 19:28, Xaver Hugl wrote:
> Oh, I just noticed: It would help if we had a CAP for this, so the
> compositor knows if the new API is supported before doing atomic tests
> with it.
No new UAPI is added for this and would be enabled by default with
atomic ioctl.
The reserved field in the struct drm_mode_atomic would be used to return
the error code. If this value is zero with a atomic_ioctl failure then
eventually should be a older kernel where this feature is not added. For
every failure on atomic_ioctl an error_code would be sent by the kernel.
Let me know if you still think a UAPI is required to get to know the
capability of this feature.
Thanks and Regards,
Arun R Murthy
--------------------
next prev parent reply other threads:[~2026-01-22 2:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 4:37 [PATCH v7 0/5] User readable error codes on atomic_ioctl failure Arun R Murthy
2026-01-06 4:37 ` [PATCH v7 1/5] drm: Define user readable error codes for atomic ioctl Arun R Murthy
2026-01-08 6:13 ` Kandpal, Suraj
2026-01-21 13:47 ` Xaver Hugl
2026-01-21 13:58 ` Xaver Hugl
2026-01-22 2:54 ` Murthy, Arun R [this message]
2026-01-22 16:23 ` Xaver Hugl
2026-01-22 2:48 ` Murthy, Arun R
2026-01-06 4:37 ` [PATCH v7 2/5] drm/atomic: Add error_code element in atomic_state Arun R Murthy
2026-01-08 6:15 ` Kandpal, Suraj
2026-01-06 4:37 ` [PATCH v7 3/5] drm/atomic: Allocate atomic_state at the beginning of atomic_ioctl Arun R Murthy
2026-01-07 11:03 ` Louis Chauvet
2026-01-22 4:41 ` Murthy, Arun R
2026-01-06 4:37 ` [PATCH v7 4/5] drm/atomic: Return user readable error in atomic_ioctl Arun R Murthy
2026-01-08 6:20 ` Kandpal, Suraj
2026-01-06 4:38 ` [PATCH v7 5/5] drm/i915/display: Error codes for async flip failures Arun R Murthy
2026-01-08 6:24 ` Kandpal, Suraj
2026-01-06 4:46 ` ✗ CI.checkpatch: warning for User readable error codes on atomic_ioctl failure (rev6) Patchwork
2026-01-06 4:47 ` ✓ CI.KUnit: success " Patchwork
2026-01-06 5:03 ` ✗ CI.checksparse: warning " Patchwork
2026-01-06 5:34 ` ✓ Xe.CI.BAT: success " Patchwork
2026-01-06 7:12 ` ✗ 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=d481788c-227f-479f-bc2a-7e30d55832bd@intel.com \
--to=arun.r.murthy@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--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=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
--cc=uma.shankar@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