Commit a8182863 authored by Daniel Vetter's avatar Daniel Vetter
Browse files

drm/docs: Small cleanup in drm-uapi.rst 



- 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@collabora.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: default avatarDavid Herrmann <dh.herrmann@gmail.com>
Signed-off-by: default avatarDaniel Vetter <daniel.vetter@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1483044517-5770-1-git-send-email-daniel.vetter@ffwll.ch
parent b834ff86

Documentation/gpu/drm-uapi.rst

+11 −14
Original line number Diff line number Diff line
@@ -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

CRA Git | Maintained and supported by SUSTech CRA and CCSE