On Wed, 11 Feb 2026, Mallesh Koujalagi <[email protected]> wrote: > Add documentation for the DRM_WEDGE_RECOVERY_COLD_RESET recovery > method introduced for handling critical errors. This method is > designated for severe errors that compromise core device functionality > and are unrecoverable via recovery mechanisms such as driver reload or PCIe > bus reset. The documentation clarifies when this recovery method should be > used and its implications for userspace applications. > > Signed-off-by: Mallesh Koujalagi <[email protected]> > --- > Documentation/gpu/drm-uapi.rst | 73 +++++++++++++++++++++++++++++++++- > 1 file changed, 72 insertions(+), 1 deletion(-) > > diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst > index d98428a592f1..eae6aef68876 100644 > --- a/Documentation/gpu/drm-uapi.rst > +++ b/Documentation/gpu/drm-uapi.rst > @@ -418,7 +418,7 @@ needed. > Recovery > -------- > > -Current implementation defines four recovery methods, out of which, drivers > +Current implementation defines five recovery methods, out of which, drivers
"several" to avoid having to update this? > can use any one, multiple or none. Method(s) of choice will be sent in the > uevent environment as ``WEDGED=<method1>[,..,<methodN>]`` in order of less to > more side-effects. See the section `Vendor Specific Recovery`_ > @@ -435,6 +435,7 @@ following expectations. > rebind unbind + bind driver > bus-reset unbind + bus reset/re-enumeration + bind > vendor-specific vendor specific recovery method > + cold-reset full device cold reset required > unknown consumer policy > =============== ======================================== > -- Jani Nikula, Intel
