From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: Jani Nikula <jani.nikula@linux.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>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>, <xaver.hugl@kde.org>,
<harry.wentland@amd.com>, <uma.shankar@intel.com>
Cc: <dri-devel@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v4 1/4] drm: Define user readable error codes for atomic ioctl
Date: Wed, 3 Sep 2025 12:12:39 +0530 [thread overview]
Message-ID: <f951ee19-83d6-43e3-82db-1025fe6ce259@intel.com> (raw)
In-Reply-To: <151f2f238b7ad4d86e503a1b0061a5bd840a55d0@intel.com>
On 02-09-2025 15:36, Jani Nikula wrote:
> On Tue, 02 Sep 2025, Arun R Murthy <arun.r.murthy@intel.com> wrote:
>> There can be multiple reasons for a failure in atomic_ioctl. Most often
>> in these error conditions -EINVAL is returned. User/Compositor would
>> have to blindly take a call on failure of this ioctl so as to use
>> ALLOW_MODESET or any. It would be good if user/compositor gets a
>> readable error code on failure so they can take proper corrections in
>> the next commit.
>> The struct drm_mode_atomic is being passed by the user/compositor which
>> holds the properties for modeset/flip. Reusing the same struct for
>> returning the error code in case of failure can save by creating a new
>> uapi/interface for returning the error code.
>> The element 'reserved' in the struct drm_mode_atomic is used for
>> returning the user readable error code. This points to the struct
>> drm_mode_atomic_err_code. Failure reasons have been initialized in
>> DRM_MODE_ATOMIC_FAILURE_REASON.
>>
>> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> Please run 'scripts/kernel-doc -Wall -none path/to/file' on all changes,
> and make sure you're not adding new errors. There are plenty, and I'm
> not going to iterate to you separately what the tool can tell you.
Ok
>> ---
>> include/uapi/drm/drm_mode.h | 41 +++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 41 insertions(+)
>>
>> diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h
>> index a122bea2559387576150236e3a88f99c24ad3138..6c4929e591b30b7a5eac472dadeeb3c9400e36df 100644
>> --- a/include/uapi/drm/drm_mode.h
>> +++ b/include/uapi/drm/drm_mode.h
>> @@ -45,6 +45,7 @@ extern "C" {
>> #define DRM_CONNECTOR_NAME_LEN 32
>> #define DRM_DISPLAY_MODE_LEN 32
>> #define DRM_PROP_NAME_LEN 32
>> +#define DRM_MODE_ATOMIC_FAILURE_STRING_LEN 64
> 64 is enough for everyone?
Should be sufficient, as we just need small meaningful error messages
that can be used for logging in user space.
To accommodate long ones, can change it to 128.
Thanks and Regards,
Arun R Murthy
--------------------
>>
>> #define DRM_MODE_TYPE_BUILTIN (1<<0) /* deprecated */
>> #define DRM_MODE_TYPE_CLOCK_C ((1<<1) | DRM_MODE_TYPE_BUILTIN) /* deprecated */
>> @@ -1157,6 +1158,46 @@ struct drm_mode_destroy_dumb {
>> DRM_MODE_ATOMIC_NONBLOCK |\
>> DRM_MODE_ATOMIC_ALLOW_MODESET)
>>
>> +/**
>> + * enum drm_mode_atomic_err_code - error codes for failures in atomic_ioctl
>> + * @DRM_MODE_ATOMIC_INVALID_API_USAGE: invallid API usage(DRM_ATOMIC not
>> + * enabled, invalid falg, page_flip event
>> + * with test-only, etc)
>> + * @DRM_MODE_ATOMIC_CRTC_NEED_FULL_MODESET: Need full modeset on this crtc
>> + * @DRM_MODE_ATOMIC_NEED_FULL_MODESET: Need full modeset on all connected crtc's
>> + * @DRM_MODE_ATOMIC_ASYN_NOTSUPP_PLANE: Aync flip not supported on this plane
>> + * DRM_MODE_ATOMIC_ASYNC_MODIFIER_NOT_SUPP: Modifier not supported by async flip
>> + * @DRM_MODE_ATOMIC_ASYNC_PROP_CHANGED: Property changed in async flip
>> + */
>> +enum drm_mode_atomic_failure_codes {
>> + DRM_MODE_ATOMIC_INVALID_API_USAGE,
>> + DRM_MODE_ATOMIC_CRTC_NEED_FULL_MODESET,
>> + DRM_MODE_ATOMIC_NEED_FULL_MODESET,
>> + DRM_MODE_ATOMIC_ASYNC_NOT_SUPP_PLANE,
>> + DRM_MODE_ATOMIC_ASYNC_MODIFIER_NOT_SUPP,
>> + DRM_MODE_ATOMIC_ASYNC_PROP_CHANGED,
>> +};
>> +
>> +/**
>> + * drm_mode_atomic_err_code - struct to store the error code
>> + *
>> + * pointer to this struct will be stored in reserved variable of
>> + * struct drm_mode_atomic to report the failure cause to the user.
>> + *
>> + * @failure_code: error codes defined in enum drm_moide_atomic_failure_code
>> + * @failure_string_ptr: pointer to user readable error message string
>> + * @failure_obj_ptr: pointer to the drm_object that caused error
>> + * @reserved: reserved for future use
>> + * @count_objs: count of drm_objects if multiple drm_objects caused error
>> + */
>> +struct drm_mode_atomic_err_code {
>> + __u64 failure_code;
>> + __u64 failure_objs_ptr;
>> + __u64 reserved;
>> + __u32 count_objs;
>> + char failure_string[DRM_MODE_ATOMIC_FAILURE_STRING_LEN];
>> +};
>> +
>> struct drm_mode_atomic {
>> __u32 flags;
>> __u32 count_objs;
next prev parent reply other threads:[~2025-09-03 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 7:47 [PATCH v4 0/4] User readable error codes on atomic_ioctl failure Arun R Murthy
2025-09-02 7:47 ` [PATCH v4 1/4] drm: Define user readable error codes for atomic ioctl Arun R Murthy
2025-09-02 10:06 ` Jani Nikula
2025-09-03 6:42 ` Murthy, Arun R [this message]
2025-09-02 7:47 ` [PATCH v4 2/4] drm/atomic: Add error_code element in atomic_state Arun R Murthy
2025-09-02 7:47 ` [PATCH v4 3/4] drm/atomic: Return user readable error in atomic_ioctl Arun R Murthy
2025-09-02 10:16 ` Jani Nikula
2025-09-03 6:52 ` Murthy, Arun R
2025-09-03 7:20 ` Jani Nikula
2025-09-02 7:47 ` [PATCH v4 4/4] drm/i915/display: Error codes for async flip failures Arun R Murthy
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=f951ee19-83d6-43e3-82db-1025fe6ce259@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=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;
as well as URLs for NNTP newsgroup(s).