[Intel-gfx] [PATCH 01/17] drm/docs: Small cleanup in drm-uapi.rst
David Herrmann
dh.herrmann at gmail.com
Fri Dec 30 11:12:48 UTC 2016
Hi
On Thu, Dec 29, 2016 at 9:48 PM, Daniel Vetter <daniel.vetter at ffwll.ch> wrote:
> - Remove the outdated hunk about driver documentation which somehow
> got misplaced here in the split-up.
>
> - Collect all the testing&validation stuff together and give the CRC
> section a heading for prettier output.
>
> Cc: Tomeu Vizoso <tomeu.vizoso at collabora.com>
> Cc: Jani Nikula <jani.nikula at intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>
> ---
> Documentation/gpu/drm-uapi.rst | 25 +++++++++++--------------
> 1 file changed, 11 insertions(+), 14 deletions(-)
Reviewed-by: David Herrmann <dh.herrmann at gmail.com>
Thanks
David
> diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
> index de3ac9f90f8f..fcc228ef5bc4 100644
> --- a/Documentation/gpu/drm-uapi.rst
> +++ b/Documentation/gpu/drm-uapi.rst
> @@ -156,8 +156,12 @@ other hand, a driver requires shared state between clients which is
> visible to user-space and accessible beyond open-file boundaries, they
> cannot support render nodes.
>
> +
> +Testing and validation
> +======================
> +
> Validating changes with IGT
> -===========================
> +---------------------------
>
> There's a collection of tests that aims to cover the whole functionality of
> DRM drivers and that can be used to check that changes to DRM drivers or the
> @@ -193,6 +197,12 @@ run-tests.sh is a wrapper around piglit that will execute the tests matching
> the -t options. A report in HTML format will be available in
> ./results/html/index.html. Results can be compared with piglit.
>
> +Display CRC Support
> +-------------------
> +
> +.. kernel-doc:: drivers/gpu/drm/drm_debugfs_crc.c
> + :doc: CRC ABI
> +
> VBlank event handling
> =====================
>
> @@ -209,16 +219,3 @@ DRM_IOCTL_MODESET_CTL
> mode setting, since on many devices the vertical blank counter is
> reset to 0 at some point during modeset. Modern drivers should not
> call this any more since with kernel mode setting it is a no-op.
> -
> -This second part of the GPU Driver Developer's Guide documents driver
> -code, implementation details and also all the driver-specific userspace
> -interfaces. Especially since all hardware-acceleration interfaces to
> -userspace are driver specific for efficiency and other reasons these
> -interfaces can be rather substantial. Hence every driver has its own
> -chapter.
> -
> -Testing and validation
> -======================
> -
> -.. kernel-doc:: drivers/gpu/drm/drm_debugfs_crc.c
> - :doc: CRC ABI
> --
> 2.7.4
>
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
More information about the Intel-gfx
mailing list