Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: airlied@gmail.com, daniel@ffwll.ch, lucas.demarchi@intel.com,
	thomas.hellstrom@linux.intel.com, rodrigo.vivi@intel.com,
	jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	tursulin@ursulin.net
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, himal.prasad.ghimiray@intel.com,
	francois.dugast@intel.com, aravind.iddamsetty@linux.intel.com,
	anshuman.gupta@intel.com, Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v4 0/3] Introduce DRM device wedged event
Date: Fri,  6 Sep 2024 15:12:22 +0530	[thread overview]
Message-ID: <20240906094225.3082162-1-raag.jadav@intel.com> (raw)

This series introduces device wedged event in DRM subsystem and uses
it in xe and i915 drivers. Detailed description in commit message.

This was earlier attempted as xe specific uevent in v1 and v2.
https://patchwork.freedesktop.org/series/136909/

v2: Change authorship to Himal (Aravind)
    Add uevent for all device wedged cases (Aravind)
v3: Generic re-implementation in DRM subsystem (Lucas)
v4: s/drm_dev_wedged/drm_dev_wedged_event
    Use drm_info() (Jani)
    Kernel doc adjustment (Aravind)
    Change authorship to Raag (Aravind)

Raag Jadav (3):
  drm: Introduce device wedged event
  drm/xe: Use device wedged event
  drm/i915: Use device wedged event

 drivers/gpu/drm/drm_drv.c             | 20 ++++++++++++++++++++
 drivers/gpu/drm/i915/gt/intel_reset.c |  2 ++
 drivers/gpu/drm/xe/xe_device.c        |  8 ++++++--
 include/drm/drm_drv.h                 |  1 +
 4 files changed, 29 insertions(+), 2 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-09-06  9:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  9:42 Raag Jadav [this message]
2024-09-06  9:42 ` [PATCH v4 1/3] drm: Introduce device wedged event Raag Jadav
2024-09-07 11:38   ` Asahi Lina
2024-09-07 15:07     ` Lucas De Marchi
2024-09-08 14:08       ` Asahi Lina
2024-09-09 20:01         ` Lucas De Marchi
2024-09-10 15:53           ` Raag Jadav
2024-09-10 16:06             ` Lucas De Marchi
2024-09-09 20:43         ` Rodrigo Vivi
2024-09-09 21:53   ` Matt Roper
2024-09-10 15:49     ` Raag Jadav
2024-09-24  9:37   ` Simona Vetter
2024-09-06  9:42 ` [PATCH v4 2/3] drm/xe: Use " Raag Jadav
2024-09-06  9:42 ` [PATCH v4 3/3] drm/i915: " Raag Jadav
2024-09-06 10:52 ` ✗ Fi.CI.CHECKPATCH: warning for Introduce DRM device wedged event (rev2) Patchwork
2024-09-06 10:52 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-06 10:59 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-10  8:53 ` ✗ Fi.CI.IGT: 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=20240906094225.3082162-1-raag.jadav@intel.com \
    --to=raag.jadav@intel.com \
    --cc=airlied@gmail.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francois.dugast@intel.com \
    --cc=himal.prasad.ghimiray@intel.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=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    /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