From: Thierry Reding <thierry.reding@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH 0/3] drm/tegra: Add support for fence FDs
Date: Thu, 11 Jan 2018 23:22:46 +0100 [thread overview]
Message-ID: <20180111222249.29105-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
This set of patches adds support for fences to Tegra DRM and complements
the fence FD support for Nouveau. Technically this isn't necessary for a
fence-based synchronization loop with Nouveau because the KMS core takes
care of all that, but engines behind host1x can use the IOCTL extensions
provided here to emit fence FDs that in turn can be used to synchronize
their jobs with either the scanout engine or the GPU.
See the following link for the Nouveau fence FD support series:
https://patchwork.freedesktop.org/series/36361/
Thierry
Mikko Perttunen (3):
gpu: host1x: Add support for DMA fences
drm/tegra: Add sync file support to submit interface
drm/tegra: Support for sync file-based fences in submit
drivers/gpu/drm/tegra/drm.c | 82 ++++++++++++---
drivers/gpu/host1x/Kconfig | 1 +
drivers/gpu/host1x/Makefile | 1 +
drivers/gpu/host1x/dev.h | 12 ++-
drivers/gpu/host1x/fence.c | 202 +++++++++++++++++++++++++++++++++++++
drivers/gpu/host1x/fence.h | 28 +++++
drivers/gpu/host1x/hw/channel_hw.c | 36 +++++--
drivers/gpu/host1x/intr.c | 11 +-
drivers/gpu/host1x/intr.h | 8 +-
drivers/gpu/host1x/syncpt.c | 2 +
include/linux/host1x.h | 12 ++-
include/uapi/drm/tegra_drm.h | 10 +-
12 files changed, 376 insertions(+), 29 deletions(-)
create mode 100644 drivers/gpu/host1x/fence.c
create mode 100644 drivers/gpu/host1x/fence.h
--
2.15.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-01-11 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 22:22 Thierry Reding [this message]
[not found] ` <20180111222249.29105-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-11 22:22 ` [PATCH 1/3] gpu: host1x: Add support for DMA fences Thierry Reding
[not found] ` <20180111222249.29105-2-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-11 23:25 ` Dmitry Osipenko
2018-01-11 22:22 ` [PATCH 2/3] drm/tegra: Add sync file support to submit interface Thierry Reding
2018-01-11 22:22 ` [PATCH 3/3] drm/tegra: Support for sync file-based fences in submit Thierry Reding
2018-01-12 10:40 ` [PATCH 0/3] drm/tegra: Add support for fence FDs Chris Wilson
[not found] ` <151575361658.23681.15835882826597063093-M6iVdVfohj6unts5RBS2dVaTQe2KTcn/@public.gmane.org>
2018-01-12 15:14 ` Thierry Reding
2018-01-12 15:38 ` Chris Wilson
[not found] ` <151577153600.24367.14807966085718429746-M6iVdVfohj6unts5RBS2dVaTQe2KTcn/@public.gmane.org>
2018-01-12 16:04 ` Thierry Reding
2018-01-15 13:57 ` Chris Wilson
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=20180111222249.29105-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=nouveau@lists.freedesktop.org \
/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