From: Arun R Murthy <arun.r.murthy@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Cc: Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
naveen1.kumar@intel.com, xaver.hugl@kde.org,
uma.shankar@intel.com, harry.wentland@amd.com,
Arun R Murthy <arun.r.murthy@intel.com>
Subject: [PATCH v2 0/4] User readable error codes on atomic_ioctl failure
Date: Wed, 30 Jul 2025 15:46:35 +0530 [thread overview]
Message-ID: <20250730-atomic-v2-0-cc02ce0263dd@intel.com> (raw)
The series focuses on providing a user readable error value on a failure
in drm_atomic_ioctl(). Usually -EINVAL is returned in most of the error
cases and it is difficult for the user to decode the error and get to
know the real cause for the error. If user gets to know the reason for
the error then corrective measurements can be taken up.
TODO: driver specific error codes are to be added and will be done in
the follow-up patches.
Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
---
Arun R Murthy (4):
drm: Define user readable error codes for atomic ioctl
drm/atomic: Add error_code element in atomic_state
drm/atomic: Return user readable error in atomic_ioctl
drm/i915/display: Error codes for async flip failures
drivers/gpu/drm/drm_atomic.c | 5 ++++
drivers/gpu/drm/drm_atomic_uapi.c | 20 ++++++++++----
drivers/gpu/drm/i915/display/intel_display.c | 4 +++
include/drm/drm_atomic.h | 7 +++++
include/uapi/drm/drm_mode.h | 40 ++++++++++++++++++++++++++++
5 files changed, 71 insertions(+), 5 deletions(-)
---
base-commit: 52ac98096df0784abd379f822ad14d6998b09154
change-id: 20250728-atomic-c9713fd357e4
Best regards,
--
Arun R Murthy <arun.r.murthy@intel.com>
next reply other threads:[~2025-07-30 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 10:16 Arun R Murthy [this message]
2025-07-30 10:16 ` [PATCH v2 1/4] drm: Define user readable error codes for atomic ioctl Arun R Murthy
2025-07-30 11:22 ` Biju Das
2025-07-30 13:45 ` Murthy, Arun R
2025-07-31 11:32 ` Xaver Hugl
2025-08-01 4:48 ` Murthy, Arun R
2025-07-30 10:16 ` [PATCH v2 2/4] drm/atomic: Add error_code element in atomic_state Arun R Murthy
2025-07-30 10:16 ` [PATCH v2 3/4] drm/atomic: Return user readable error in atomic_ioctl Arun R Murthy
2025-07-30 13:14 ` Harry Wentland
2025-07-30 13:55 ` Murthy, Arun R
2025-07-30 14:19 ` Harry Wentland
2025-07-30 10:16 ` [PATCH v2 4/4] drm/i915/display: Error codes for async flip failures Arun R Murthy
2025-07-30 10:43 ` ✓ CI.KUnit: success for User readable error codes on atomic_ioctl failure Patchwork
2025-07-30 10:58 ` ✗ CI.checksparse: warning " Patchwork
2025-07-30 11:22 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-30 12:57 ` ✗ i915.CI.BAT: failure " Patchwork
2025-07-30 13:25 ` ✗ Xe.CI.Full: " 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=20250730-atomic-v2-0-cc02ce0263dd@intel.com \
--to=arun.r.murthy@intel.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=naveen1.kumar@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.