From: Mikko Perttunen <mperttunen@nvidia.com>
To: "Thierry Reding" <thierry.reding@kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
"open list:DMA BUFFER SHARING
FRAMEWORK:Keyword:bdma_?:buf|fence|resvb"
<linux-media@vger.kernel.org>,
"moderated list:DMA BUFFER SHARING
FRAMEWORK:Keyword:bdma_?:buf|fence|resvb"
<linaro-mm-sig@lists.linaro.org>,
Mikko Perttunen <mperttunen@nvidia.com>,
Dan Carpenter <error27@gmail.com>
Subject: [PATCH 0/6] Fixes and improvements to syncobj handling in TegraDRM submit path
Date: Thu, 30 Jul 2026 13:44:40 +0900 [thread overview]
Message-ID: <20260730-b4-host1x-syncobj-wait-v1-0-afa730410392@nvidia.com> (raw)
The syncobj code in the TegraDRM submit path has been quite broken for a
while. Let's get it in (better) shape for unstaging.
The first part of the series, patches 1-4 are fixes and and a cosmetic
improvement. They fix the syncobj handling, though it remains unoptimal
- CPU waited.
Patch 5 adds host1x_fence_extract, necessary to allow other drivers to
see inside syncpoint fences and program hardware to do direct waits.
Patch 6 adds support to the TegraDRM submit path for waiting such fences
directly using Host1x channel commands.
Tested on Tegra234.
Best regards
Mikko
Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
---
Mikko Perttunen (6):
drm/tegra: Fix syncobj_in wait return value check
drm/tegra: Don't pass an ERR_PTR to drm_syncobj_replace_fence()
drm/tegra: Drop reference on postfence
drm/tegra: Remove unused includes from submit.c
gpu: host1x: Add host1x_fence_extract()
drm/tegra: Wait for syncpoint syncobj_in fences in hardware
drivers/gpu/drm/tegra/submit.c | 109 +++++++++++++++++++++++++++++++++++------
drivers/gpu/host1x/fence.c | 43 ++++++++++++++++
include/linux/host1x.h | 2 +
include/uapi/drm/tegra_drm.h | 4 +-
4 files changed, 140 insertions(+), 18 deletions(-)
---
base-commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
change-id: 20260727-b4-host1x-syncobj-wait-84284ac2838c
next reply other threads:[~2026-07-30 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 4:44 Mikko Perttunen [this message]
2026-07-30 4:44 ` [PATCH 1/6] drm/tegra: Fix syncobj_in wait return value check Mikko Perttunen
2026-07-30 4:44 ` [PATCH 2/6] drm/tegra: Don't pass an ERR_PTR to drm_syncobj_replace_fence() Mikko Perttunen
2026-07-30 4:44 ` [PATCH 3/6] drm/tegra: Drop reference on postfence Mikko Perttunen
2026-07-30 4:44 ` [PATCH 4/6] drm/tegra: Remove unused includes from submit.c Mikko Perttunen
2026-07-30 4:44 ` [PATCH 5/6] gpu: host1x: Add host1x_fence_extract() Mikko Perttunen
2026-07-30 4:44 ` [PATCH 6/6] drm/tegra: Wait for syncpoint syncobj_in fences in hardware Mikko Perttunen
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=20260730-b4-host1x-syncobj-wait-v1-0-afa730410392@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=error27@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=thierry.reding@kernel.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