dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: Re: [PATCH libdrm v2 00/25] Update Tegra support
Date: Thu, 17 Feb 2022 23:02:53 +0300	[thread overview]
Message-ID: <fb059f6f-013a-4a7e-55a7-81acbdda80fc@gmail.com> (raw)
In-Reply-To: <20220217191625.2534521-1-thierry.reding@gmail.com>

17.02.2022 22:16, Thierry Reding пишет:
> From: Thierry Reding <treding@nvidia.com>
> 
> Hi all,
> 
> this is the userspace part of the kernel patches that were recently
> merged into drm-next:
> 
>   https://patchwork.freedesktop.org/series/92378/
> 
> The goal is to provide a userspace implementation of the UAPI exposed by
> the kernel and show its usage in some test programs that can also be
> used for basic sanity testing. More complete userspace implementations
> are available here:
> 
>   * https://github.com/cyndis/vaapi-tegra-driver
>   * https://github.com/grate-driver/xf86-video-opentegra
>   * https://github.com/grate-driver/grate
> 
> Changes in v2:
> - implement vic_clear() as a helper using ->fill() (Michał Mirosław)
> - rebase and fix a couple of Meson errors/warnings
> 
> Thierry
> 
> Thierry Reding (25):
>   tegra: Indent according to .editorconfig
>   tegra: Remove unused IOCTL implementations
>   tegra: Extract common buffer object allocation code
>   tegra: Fix mmap() of GEM buffer objects
>   tegra: Add flink helpers
>   tegra: Add PRIME support helpers
>   tegra: Make API more consistent
>   tegra: Install tegra-openclose test
>   tegra: Update for new UABI
>   tegra: Include private.h in list of source files
>   tegra: Add channel APIs
>   tegra: Add job and push buffer APIs
>   tegra: Add syncpoint APIs
>   tests: tegra: Add helper library for tests
>   tests: tegra: Add gr2d-fill test
>   tests: tegra: Add syncpt-wait test
>   tests: tegra: Add syncpoint timeout test
>   tests: tegra: Add VIC support
>   tests: tegra: Add VIC 3.0 support
>   tests: tegra: Add VIC 4.0 support
>   tests: tegra: Add VIC 4.1 support
>   tests: tegra: Add VIC 4.2 support
>   tests: tegra: Add VIC clear test
>   tests: tegra: Add VIC blit test
>   tests: tegra: Add VIC flip test
> 
>  include/drm/tegra_drm.h      | 429 +++++++++++++++++++++++--
>  tegra/channel.c              | 195 ++++++++++++
>  tegra/job.c                  | 187 +++++++++++
>  tegra/meson.build            |   7 +-
>  tegra/private.h              |  85 ++++-
>  tegra/pushbuf.c              | 184 +++++++++++
>  tegra/syncpt.c               | 101 ++++++
>  tegra/tegra-symbols.txt      |  27 +-
>  tegra/tegra.c                | 386 +++++++++++-----------
>  tegra/tegra.h                |  95 +++++-
>  tests/tegra/.gitignore       |   3 +-
>  tests/tegra/drm-test-tegra.c | 147 +++++++++
>  tests/tegra/drm-test-tegra.h |  55 ++++
>  tests/tegra/drm-test.c       | 248 +++++++++++++++
>  tests/tegra/drm-test.h       |  72 +++++
>  tests/tegra/gr2d-fill.c      | 146 +++++++++
>  tests/tegra/host1x.h         |  34 ++
>  tests/tegra/meson.build      |  88 +++++-
>  tests/tegra/openclose.c      |  52 +--
>  tests/tegra/syncpt-timeout.c | 163 ++++++++++
>  tests/tegra/syncpt-wait.c    | 151 +++++++++
>  tests/tegra/vic-blit.c       | 333 +++++++++++++++++++
>  tests/tegra/vic-clear.c      | 173 ++++++++++
>  tests/tegra/vic-flip.c       | 333 +++++++++++++++++++
>  tests/tegra/vic.c            | 184 +++++++++++
>  tests/tegra/vic.h            | 181 +++++++++++
>  tests/tegra/vic30.c          | 458 +++++++++++++++++++++++++++
>  tests/tegra/vic30.h          | 439 ++++++++++++++++++++++++++
>  tests/tegra/vic40.c          | 370 ++++++++++++++++++++++
>  tests/tegra/vic40.h          | 285 +++++++++++++++++
>  tests/tegra/vic41.c          | 374 ++++++++++++++++++++++
>  tests/tegra/vic41.h          | 372 ++++++++++++++++++++++
>  tests/tegra/vic42.c          | 374 ++++++++++++++++++++++
>  tests/tegra/vic42.h          | 597 +++++++++++++++++++++++++++++++++++
>  34 files changed, 7068 insertions(+), 260 deletions(-)


Why do we need these tests in libdrm? Why not IGT?


  parent reply	other threads:[~2022-02-17 20:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 19:16 [PATCH libdrm v2 00/25] Update Tegra support Thierry Reding
2022-02-17 19:16 ` [PATCH libdrm v2 01/25] tegra: Indent according to .editorconfig Thierry Reding
2022-02-17 19:16 ` [PATCH libdrm v2 02/25] tegra: Remove unused IOCTL implementations Thierry Reding
2022-02-24 16:52   ` Dmitry Osipenko
2022-02-17 19:16 ` [PATCH libdrm v2 03/25] tegra: Extract common buffer object allocation code Thierry Reding
2022-02-17 19:16 ` [PATCH libdrm v2 04/25] tegra: Fix mmap() of GEM buffer objects Thierry Reding
2022-02-17 19:16 ` [PATCH libdrm v2 05/25] tegra: Add flink helpers Thierry Reding
2022-02-24 17:18   ` Dmitry Osipenko
2022-02-17 20:02 ` Dmitry Osipenko [this message]
2022-02-17 21:37   ` [PATCH libdrm v2 00/25] Update Tegra support Thierry Reding
2022-02-18 14:16     ` Dmitry Osipenko
2022-02-18 19:49       ` Dmitry Osipenko
2022-02-18  9:31 ` Mikko Perttunen
2022-02-21 20:29   ` Dmitry Osipenko
2022-02-22  8:41     ` Mikko Perttunen
2022-02-23 15:01       ` Thierry Reding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb059f6f-013a-4a7e-55a7-81acbdda80fc@gmail.com \
    --to=digetx@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=thierry.reding@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox