On 12/1/22 12:11, Maxime Ripard wrote:

Now that we have VC4-specific tests in place, let's document them properly.

Signed-off-by: Maxime Ripard maxime@cerno.tech

Reviewed-by: Maíra Canal mcanal@igalia.com

Just a small nit below.

---

Documentation/gpu/vc4.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)

diff --git a/Documentation/gpu/vc4.rst b/Documentation/gpu/vc4.rst index 5df1d98b9544..a2375f1584e6 100644 --- a/Documentation/gpu/vc4.rst +++ b/Documentation/gpu/vc4.rst @@ -54,6 +54,22 @@ VEC (Composite TV out) encoder .. kernel-doc:: drivers/gpu/drm/vc4/vc4_vec.c :doc: VC4 SDTV module +KUnit Tests +===========

+The VC4 Driver uses KUnit to perform driver-specific unit and +integration tests.

+These tests are using a mock driver and can be ran using the +command::

• ./tools/testing/kunit/kunit.py run \

• --kunitconfig=drivers/gpu/drm/vc4/tests/.kunitconfig \
  

• --cross_compile aarch64-linux-gnu- --arch arm64
  

I believe you could use a code block here, like:

.. code-block:: bash $ ./tools/testing/kunit/kunit.py run \ --kunitconfig=drivers/gpu/drm/vc4/tests/.kunitconfig \ --cross_compile aarch64-linux-gnu- --arch arm64

You could also mention that you can run the tests with --arch arm.

Best Regards, - Maíra Canal

+Parts of the driver that are currently covered by tests are:

• • The HVS to PixelValve dynamic FIFO assignment, for the BCM2835-7
• and BCM2711.

• Memory Management and 3D Command Submission