Applied to drm-misc-fixes
On 5/28/2025 5:42 PM, Jacek Lawrynowicz wrote:
> From: Karol Wachowski
>
> Trigger full device recovery when the driver fails to restore device state
> via engine reset and resume operations. This is necessary because, even if
> submissions from a faulty context are blo
On 6/2/25 06:05, Jacek Lawrynowicz wrote:
Hi,
On 5/28/2025 7:53 PM, Lizhi Hou wrote:
On 5/28/25 08:42, Jacek Lawrynowicz wrote:
From: Karol Wachowski
Trigger full device recovery when the driver fails to restore device state
via engine reset and resume operations. This is necessary because
Hi,
On 5/28/2025 7:53 PM, Lizhi Hou wrote:
>
> On 5/28/25 08:42, Jacek Lawrynowicz wrote:
>> From: Karol Wachowski
>>
>> Trigger full device recovery when the driver fails to restore device state
>> via engine reset and resume operations. This is necessary because, even if
>> submissions from a
On 5/28/25 08:42, Jacek Lawrynowicz wrote:
From: Karol Wachowski
Trigger full device recovery when the driver fails to restore device state
via engine reset and resume operations. This is necessary because, even if
submissions from a faulty context are blocked, the NPU may still process
previ
From: Karol Wachowski
Trigger full device recovery when the driver fails to restore device state
via engine reset and resume operations. This is necessary because, even if
submissions from a faulty context are blocked, the NPU may still process
previously submitted faulty jobs if the engine reset
