From: Christian König Date: Mon, 26 Aug 2024 12:25:39 +0000 (+0200) Subject: dma-buf: give examples of error codes to use X-Git-Tag: v6.13-rc1~122^2~23^2~94 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a401bd1264b400f96a4cf61ed3fc144008e97a4e;p=thirdparty%2Fkernel%2Flinux.git dma-buf: give examples of error codes to use The dma_fence_set_error() function allows to set an error code on a dma_fence object before it is signaled. Document some of the potential error codes drivers should use and especially what they mean. Signed-off-by: Christian König Acked-by: Daniel Vetter Reviewed-by: Alex Deucher Link: https://patchwork.freedesktop.org/patch/msgid/20240826122541.85663-2-christian.koenig@amd.com --- diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h index e06bad467f55e..e7ad819962e3e 100644 --- a/include/linux/dma-fence.h +++ b/include/linux/dma-fence.h @@ -574,6 +574,12 @@ int dma_fence_get_status(struct dma_fence *fence); * rather than success. This must be set before signaling (so that the value * is visible before any waiters on the signal callback are woken). This * helper exists to help catching erroneous setting of #dma_fence.error. + * + * Examples of error codes which drivers should use: + * + * * %-ENODATA This operation produced no data, no other operation affected. + * * %-ECANCELED All operations from the same context have been canceled. + * * %-ETIME Operation caused a timeout and potentially device reset. */ static inline void dma_fence_set_error(struct dma_fence *fence, int error)