From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Vikash Garodia <quic_vgarodia@quicinc.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Tomasz Figa <tfiga@chromium.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCHv3] media: venus: provide video device lock
Date: Fri, 26 May 2023 12:35:31 +0900 [thread overview]
Message-ID: <20230526033531.GA2810326@google.com> (raw)
In-Reply-To: <3e395f16-79f0-501f-21f1-70645d6137c2@quicinc.com>
On (23/05/25 16:32), Vikash Garodia wrote:
> > * @sequence_out: a sequence counter for output queue
> > * @m2m_dev: a reference to m2m device structure
> > * @m2m_ctx: a reference to m2m context structure
> > + * @ctx_queue_lock: a lock to serialize video device ioctl calls
> suggestion: we can keep this as ctx_q_lock.
Ack
> > v4l2_fh_init(&inst->fh, core->vdev_dec);
> >
> > + inst->m2m_ctx->q_lock = &inst->ctx_queue_lock;
> Better to do this in queue_init callback i.e "m2m_queue_init" in vdec.c.
> src_vq->lock = &inst->ctx_q_lock;
> ...
> dst_vq->lock = src_vq->lock;
Ack
> > @@ -1483,6 +1484,7 @@ static int venc_open(struct file *file)
> >
> > v4l2_fh_init(&inst->fh, core->vdev_enc);
> >
> > + inst->m2m_ctx->q_lock = &inst->ctx_queue_lock;
> Same comment applies here. This can be moved to "m2m_queue_init" in venc.c.
Ack
next prev parent reply other threads:[~2023-05-26 3:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 1:36 [PATCH] media: venus: provide video device lock Sergey Senozhatsky
2023-05-24 12:40 ` Sergey Senozhatsky
2023-05-24 13:56 ` [PATCHv2] " Sergey Senozhatsky
2023-05-24 14:12 ` [PATCHv3] " Sergey Senozhatsky
2023-05-24 14:29 ` Bryan O'Donoghue
2023-05-24 14:44 ` Hans Verkuil
2023-05-24 16:36 ` Vikash Garodia
2023-05-25 0:53 ` Sergey Senozhatsky
2023-05-25 11:02 ` Vikash Garodia
2023-05-26 3:35 ` Sergey Senozhatsky [this message]
2023-05-25 7:22 ` Hans Verkuil
2023-05-25 8:59 ` Sergey Senozhatsky
2023-05-25 9:03 ` Hans Verkuil
2023-06-01 10:16 ` Vikash Garodia
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=20230526033531.GA2810326@google.com \
--to=senozhatsky@chromium.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=quic_vgarodia@quicinc.com \
--cc=stanimir.k.varbanov@gmail.com \
--cc=tfiga@chromium.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