Re: [PATCH v1 1/3] drm/doc: Update documentation for 'none' recovery method

[Rodrigo Vivi <rodrigo.vivi@intel.com>]

On Tue, Mar 03, 2026 at 04:35:17PM +0530, Raag Jadav wrote:
> Expand 'none' recovery method for wedged event to include debug cases
> where driver wants to hint "no recovery" without resetting the device
> from driver context.
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
>  Documentation/gpu/drm-uapi.rst | 12 +++++-------
>  1 file changed, 5 insertions(+), 7 deletions(-)
> 
> diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
> index d98428a592f1..af20136108b7 100644
> --- a/Documentation/gpu/drm-uapi.rst
> +++ b/Documentation/gpu/drm-uapi.rst
> @@ -439,13 +439,11 @@ following expectations.
>      =============== ========================================
>  
>  The only exception to this is ``WEDGED=none``, which signifies that the device

I don't believe it is an 'exception'. The recovery method is none. It means 'do nothing
to recover'.

> -was temporarily 'wedged' at some point but was recovered from driver context
> -using device specific methods like reset. No explicit recovery is expected from
> -the consumer in this case, but it can still take additional steps like gathering
> -telemetry information (devcoredump, syslog). This is useful because the first
> -hang is usually the most critical one which can result in consequential hangs or
> -complete wedging.
> -
> +was temporarily 'wedged' at some point but no explicit recovery is expected

temporarily or definitive it doesn't matter. none still means 'do nothing to recover'.

> +from the consumer in this case. The consumer can still try to gather telemetry
> +information (devcoredump, syslog) for debug purpose in order to root cause the
> +hang. This is useful because the first hang is usually the most critical one
> +which can result in consequential hangs or complete wedging.

What about replacing this entire sentence to something like:

WEDGED=none indicates that no recovery action is expected from userspace—regardless of whether the driver already handled the condition—and consumers may optionally collect telemetry (e.g., devcoredump, syslog) for debugging.

(AI assisted text)

>  
>  Vendor Specific Recovery
>  ------------------------
> -- 
> 2.43.0
>