From: "Christian König" <christian.koenig@amd.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
airlied@gmail.com, simona@ffwll.ch, lucas.demarchi@intel.com,
thomas.hellstrom@linux.intel.com, jani.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com,
joonas.lahtinen@linux.intel.com, tursulin@ursulin.net,
lina@asahilina.net, 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,
andi.shyti@linux.intel.com, matthew.d.roper@intel.com,
boris.brezillon@collabora.com, adrian.larumbe@collabora.com,
kernel@collabora.com, maraeo@gmail.com, friedrich.vock@gmx.de,
michel@daenzer.net, joshua@froggi.es, alexander.deucher@amd.com,
andrealmeid@igalia.com, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v7 1/5] drm: Introduce device wedged event
Date: Fri, 18 Oct 2024 14:54:38 +0200 [thread overview]
Message-ID: <da5d8d7d-cbf3-403d-89f9-465cd730ef0a@amd.com> (raw)
In-Reply-To: <ZxJYm6epuuConWdz@black.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Am 18.10.24 um 14:46 schrieb Raag Jadav:
>> As far as I can see this makes the enum how to recover the device
>> superfluous because you will most likely always need a bus reset to get out
>> of this again.
> That depends on the kind of fault the device has encountered and the bus it is
> sitting on. There could be buses that don't support reset.
That is even more an argument to not expose this in the uevent.
Getting the device working again is strongly device dependent and can't
be handled in a generic way.
Regards,
Christian.
>
> Raag
[-- Attachment #2: Type: text/html, Size: 1179 bytes --]
next prev parent reply other threads:[~2024-10-18 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930073845.347326-1-raag.jadav@intel.com>
[not found] ` <20240930073845.347326-2-raag.jadav@intel.com>
2024-10-17 2:47 ` [PATCH v7 1/5] drm: Introduce device wedged event Raag Jadav
2024-10-17 7:59 ` Christian König
2024-10-17 16:43 ` Rodrigo Vivi
2024-10-18 10:58 ` Christian König
2024-10-18 12:46 ` Raag Jadav
2024-10-18 12:54 ` Christian König [this message]
2024-10-18 14:09 ` Raag Jadav
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=da5d8d7d-cbf3-403d-89f9-465cd730ef0a@amd.com \
--to=christian.koenig@amd.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andi.shyti@linux.intel.com \
--cc=andrealmeid@igalia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=friedrich.vock@gmx.de \
--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=joshua@froggi.es \
--cc=kernel@collabora.com \
--cc=lina@asahilina.net \
--cc=lucas.demarchi@intel.com \
--cc=maraeo@gmail.com \
--cc=matthew.d.roper@intel.com \
--cc=michel@daenzer.net \
--cc=raag.jadav@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--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