From: Philipp Zabel <p.zabel@pengutronix.de>
To: Jean-Michel Hautbois <jean-michel.hautbois@veo-labs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH] [media] coda: implement encoder stop command
Date: Thu, 02 Mar 2017 11:16:22 +0100 [thread overview]
Message-ID: <1488449782.2301.6.camel@pengutronix.de> (raw)
In-Reply-To: <CAH-u=833MgX4ZD07db4Reg+N6ch7Q35_7qt0Prn-6THYO0wFTQ@mail.gmail.com>
Hi Jean-Michel,
On Thu, 2017-03-02 at 11:02 +0100, Jean-Michel Hautbois wrote:
> Hi Philipp,
>
> 2017-03-02 10:51 GMT+01:00 Philipp Zabel <p.zabel@pengutronix.de>:
> > There is no need to call v4l2_m2m_try_schedule to kick off draining the
> > bitstream buffer for the encoder, but we have to wake up the destination
> > queue in case there are no new OUTPUT buffers to be encoded and userspace
> > is already polling for new CAPTURE buffers.
> >
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > ---
> > drivers/media/platform/coda/coda-common.c | 47 +++++++++++++++++++++++++++++++
> > 1 file changed, 47 insertions(+)
> >
> > diff --git a/drivers/media/platform/coda/coda-common.c b/drivers/media/platform/coda/coda-common.c
> > index e1a2e8c70db01..085bbdb0d361b 100644
> > --- a/drivers/media/platform/coda/coda-common.c
> > +++ b/drivers/media/platform/coda/coda-common.c
> > @@ -881,6 +881,47 @@ static int coda_g_selection(struct file *file, void *fh,
> > return 0;
> > }
> >
> > +static int coda_try_encoder_cmd(struct file *file, void *fh,
> > + struct v4l2_encoder_cmd *ec)
> > +{
> > + if (ec->cmd != V4L2_ENC_CMD_STOP)
> > + return -EINVAL;
> > +
> > + if (ec->flags & V4L2_ENC_CMD_STOP_AT_GOP_END)
> > + return -EINVAL;
> > +
> > + return 0;
> > +}
> > +
> > +static int coda_encoder_cmd(struct file *file, void *fh,
> > + struct v4l2_encoder_cmd *ec)
> > +{
> > + struct coda_ctx *ctx = fh_to_ctx(fh);
> > + struct vb2_queue *dst_vq;
> > + int ret;
> > +
> > + ret = coda_try_encoder_cmd(file, fh, ec);
> > + if (ret < 0)
> > + return ret;
> > +
> > + /* Ignore encoder stop command silently in decoder context */
> > + if (ctx->inst_type != CODA_INST_ENCODER)
> > + return 0;
> > +
> > + /* Set the stream-end flag on this context */
> > + ctx->bit_stream_param |= CODA_BIT_STREAM_END_FLAG;
>
> Why aren't you calling coda_bit_stream_end_flag() ?
Because that additionally does:
/* If this context is currently running, update the hardware flag */
if ((dev->devtype->product == CODA_960) &&
coda_isbusy(dev) &&
(ctx->idx == coda_read(dev, CODA_REG_BIT_RUN_INDEX))) {
coda_write(dev, ctx->bit_stream_param,
CODA_REG_BIT_BIT_STREAM_PARAM);
}
to kick a potentially hanging decode picture run. This is unnecessary in the
encoder case.
We only need the flag set to make coda_buf_is_end_of_stream return true
and thereby make coda_m2m_buf_done set the V4L2_BUF_FLAG_LAST on the
buffer and emit the EOS event.
regards
Philipp
next prev parent reply other threads:[~2017-03-02 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 9:51 [PATCH] [media] coda: implement encoder stop command Philipp Zabel
2017-03-02 10:02 ` Jean-Michel Hautbois
2017-03-02 10:16 ` Philipp Zabel [this message]
2017-03-02 16:30 ` Jean-Michel Hautbois
2017-03-03 11:50 ` Philipp Zabel
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=1488449782.2301.6.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=jean-michel.hautbois@veo-labs.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.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;
as well as URLs for NNTP newsgroup(s).