From: Mikko Perttunen <mperttunen@nvidia.com>
To: thierry.reding@gmail.com, jonathanh@nvidia.com, digetx@gmail.com,
airlied@linux.ie, daniel@ffwll.ch
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH v6 03/14] gpu: host1x: Add job release callback
Date: Sun, 30 May 2021 15:21:45 +0300 [thread overview]
Message-ID: <20210530122156.3292479-4-mperttunen@nvidia.com> (raw)
In-Reply-To: <20210530122156.3292479-1-mperttunen@nvidia.com>
Add a callback field to the job structure, to be called just before
the job is to be freed. This allows the job's submitter to clean
up any of its own state, like decrement runtime PM refcounts.
Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
---
drivers/gpu/host1x/job.c | 3 +++
include/linux/host1x.h | 4 ++++
2 files changed, 7 insertions(+)
diff --git a/drivers/gpu/host1x/job.c b/drivers/gpu/host1x/job.c
index 8f59b34672c2..09097e19c0d0 100644
--- a/drivers/gpu/host1x/job.c
+++ b/drivers/gpu/host1x/job.c
@@ -79,6 +79,9 @@ static void job_free(struct kref *ref)
{
struct host1x_job *job = container_of(ref, struct host1x_job, ref);
+ if (job->release)
+ job->release(job);
+
if (job->waiter)
host1x_intr_put_ref(job->syncpt->host, job->syncpt->id,
job->waiter, false);
diff --git a/include/linux/host1x.h b/include/linux/host1x.h
index 98dfb72e6c77..432125804208 100644
--- a/include/linux/host1x.h
+++ b/include/linux/host1x.h
@@ -265,6 +265,10 @@ struct host1x_job {
/* Fast-forward syncpoint increments on job timeout */
bool syncpt_recovery;
+
+ /* Callback called when job is freed */
+ void (*release)(struct host1x_job *job);
+ void *user_data;
};
struct host1x_job *host1x_job_alloc(struct host1x_channel *ch,
--
2.30.1
next prev parent reply other threads:[~2021-05-30 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 12:21 [PATCH v6 00/14] TegraDRM UAPI Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 01/14] gpu: host1x: Add DMA fence implementation Mikko Perttunen
2021-05-30 13:45 ` kernel test robot
2021-05-30 12:21 ` [PATCH v6 02/14] gpu: host1x: Add no-recovery mode Mikko Perttunen
2021-05-30 12:21 ` Mikko Perttunen [this message]
2021-05-30 12:21 ` [PATCH v6 04/14] gpu: host1x: Add support for syncpoint waits in CDMA pushbuffer Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 05/14] drm/tegra: Extract tegra_gem_lookup Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 06/14] drm/tegra: Add new UAPI to header Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 07/14] drm/tegra: Boot VIC during runtime PM resume Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 08/14] drm/tegra: Allocate per-engine channel in core code Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 09/14] drm/tegra: Implement new UAPI Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 10/14] drm/tegra: Implement syncpoint management UAPI Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 11/14] drm/tegra: Implement syncpoint wait UAPI Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 12/14] drm/tegra: Implement job submission part of new UAPI Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 13/14] drm/tegra: Add job firewall Mikko Perttunen
2021-05-30 12:21 ` [PATCH v6 14/14] drm/tegra: Bump driver version 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=20210530122156.3292479-4-mperttunen@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--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