summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/host1x/hw
diff options
context:
space:
mode:
authorMikko Perttunen <mperttunen@nvidia.com>2023-01-19 14:09:21 +0100
committerThierry Reding <treding@nvidia.com>2023-01-26 15:55:38 +0100
commitd5179020f5ce44fd449790a9c12ef6c1a90a2ca7 (patch)
treeb23507f69bf4ea56a40f7261a67ad8a8a04c5f71 /drivers/gpu/host1x/hw
parentgpu: host1x: Rewrite syncpoint interrupt handling (diff)
downloadlinux-d5179020f5ce44fd449790a9c12ef6c1a90a2ca7.tar.xz
linux-d5179020f5ce44fd449790a9c12ef6c1a90a2ca7.zip
gpu: host1x: External timeout/cancellation for fences
Currently all fences have a 30 second timeout to ensure they are cleaned up if the fence never completes otherwise. However, this one size fits all solution doesn't actually fit in every case, such as syncpoint waiting where we want to be able to have timeouts longer than 30 seconds. As such, we want to be able to give control over fence cancellation to the caller (and maybe eventually get rid of the internal timeout altogether). Here we add this cancellation mechanism by essentially adding a function for entering the timeout path by function call, and changing the syncpoint wait function to use it. Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com> Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'drivers/gpu/host1x/hw')
-rw-r--r--drivers/gpu/host1x/hw/channel_hw.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/gpu/host1x/hw/channel_hw.c b/drivers/gpu/host1x/hw/channel_hw.c
index 8a3119fc5a77..0a528573a792 100644
--- a/drivers/gpu/host1x/hw/channel_hw.c
+++ b/drivers/gpu/host1x/hw/channel_hw.c
@@ -325,7 +325,7 @@ static int channel_submit(struct host1x_job *job)
* Create fence before submitting job to HW to avoid job completing
* before the fence is set up.
*/
- job->fence = host1x_fence_create(sp, syncval);
+ job->fence = host1x_fence_create(sp, syncval, true);
if (WARN(IS_ERR(job->fence), "Failed to create submit complete fence")) {
job->fence = NULL;
} else {