[PATCH v3 1/7] drm: Add a vendor-specific recovery method to device wedged uevent

Riana Tauro riana.tauro at intel.com
Thu Jul 3 06:50:23 UTC 2025



On 7/3/2025 12:10 PM, Raag Jadav wrote:
> On Thu, Jul 03, 2025 at 10:50:53AM +0530, Riana Tauro wrote:
>> On 7/3/2025 9:36 AM, Raag Jadav wrote:
>>> On Wed, Jul 02, 2025 at 07:41:11PM +0530, Riana Tauro wrote:
>>>> Certain errors can cause the device to be wedged and may
>>>> require a vendor specific recovery method to restore normal
>>>> operation.
>>>>
>>>> Add a recovery method 'WEDGED=vendor-specific' for such errors. Vendors
>>>> must provide additional recovery documentation if this method
>>>> is used.
> 
> ...
> 
>>>> diff --git a/include/drm/drm_device.h b/include/drm/drm_device.h
>>>> index 08b3b2467c4c..40a4caaa6313 100644
>>>> --- a/include/drm/drm_device.h
>>>> +++ b/include/drm/drm_device.h
>>>> @@ -26,10 +26,14 @@ struct pci_controller;
>>>>     * Recovery methods for wedged device in order of less to more side-effects.
>>>>     * To be used with drm_dev_wedged_event() as recovery @method. Callers can
>>>>     * use any one, multiple (or'd) or none depending on their needs.
>>>> + *
>>>> + * If DRM_WEDGE_RECOVERY_VENDOR method is used, vendors must provide additional
>>>> + * documentation outlining further recovery steps.
>>>
>>> The original documentation is sufficient so let's not duplicate specific
>>> cases here.
>>
>> Added it here so anyone checking the code directly is aware.
> 
> Then a reference to uapi doc would be more useful.

That should be okay. Will do that

Thanks
Riana

> 
> Raag



More information about the dri-devel mailing list