From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: alex.zuo@intel.com, jonathan.cavitt@intel.com,
michal.wajdeczko@intel.com, raag.jadav@intel.com,
andi.shyti@linux.intel.com, jani.nikula@intel.com
Subject: [PATCH v6 0/3] drm/xe: Refactor I2C and HECI error messages
Date: Thu, 3 Sep 2026 03:58:48 +0800 [thread overview]
Message-ID: <20260902195851.306669-1-jonathan.cavitt@intel.com> (raw)
Update xe_heci_gsc.c and xe_i2c.c to use the xe error reporting helper
functions in xe_printk.h instead of directly calling the associated drm
print functions from drm_print.h. While we're here, we should update
the error messages to print the error codes in a more friendly way.
This necessitates creating a new helper function - xe_warn_once() - as
drm_warn_once() currently has no equivalent helper function in
xe_printk.h.
Jonathan Cavitt (3):
drm/xe/printk: Add xe_warn_once()
drm/xe/heci: Use xe print functions in xe_heci_gsc.c
drm/xe/i2c: Use xe print functions in xe_i2c.c
drivers/gpu/drm/xe/xe_heci_gsc.c | 21 ++++++++++-----------
drivers/gpu/drm/xe/xe_i2c.c | 6 +++---
drivers/gpu/drm/xe/xe_printk.h | 3 +++
3 files changed, 16 insertions(+), 14 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-02 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:58 Jonathan Cavitt [this message]
2026-09-02 19:58 ` [PATCH v6 1/3] drm/xe/printk: Add xe_warn_once() Jonathan Cavitt
2026-09-02 19:58 ` [PATCH v6 2/3] drm/xe/heci: Use xe print functions in xe_heci_gsc.c Jonathan Cavitt
2026-09-02 19:58 ` [PATCH v6 3/3] drm/xe/i2c: Use xe print functions in xe_i2c.c Jonathan Cavitt
2026-09-02 20:06 ` ✓ CI.KUnit: success for drm/xe: Refactor I2C and HECI error messages Patchwork
2026-09-02 21:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-03 11:32 ` ✗ 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=20260902195851.306669-1-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=raag.jadav@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