From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: Sylwester Nawrocki <snjw23@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-media@vger.kernel.org, hverkuil@xs4all.nl,
kyungmin.park@samsung.com, shawn.guo@linaro.org,
richard.zhao@linaro.org, fabio.estevam@freescale.com,
kernel@pengutronix.de, s.hauer@pengutronix.de,
r.schwebel@pengutronix.de, Pawel Osciak <p.osciak@gmail.com>
Subject: Re: MEM2MEM devices: how to handle sequence number?
Date: Mon, 2 Jan 2012 12:06:04 +0100 [thread overview]
Message-ID: <201201021206.06397.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <CACKLOr3cZvM-oH+s7tcfnnDAsrqSP6TVV9UVhJ6o4FJz8RxmiA@mail.gmail.com>
Hi Javier,
On Monday 02 January 2012 11:22:54 javier Martin wrote:
> Hi,
> i've just arrived the office after holidays and it seems you have
> agreed some solution to the sequence number issue.
>
> As I understand, for a case where there is 1:1 correspondence between
> input and output (which is my case) I should do the following:
>
> - keep an internal frame counter associated with the output queue.
> - return the frame number when the user calls VIDIOC_QBUF on the output.
> - pass the output frame number to the capture queue in a 1:1 basis
That's right.
> So in my chain of three processed nodes each node has its own internal
> frame counter and frame loss should be checked at the video source.
You can use an internal frame counter for each node if needed for internal
operation, but that's not required from the userspace point of view.
> Is that OK?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-01-02 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 14:34 MEM2MEM devices: how to handle sequence number? javier Martin
2011-12-23 7:09 ` Marek Szyprowski
2011-12-23 11:28 ` Laurent Pinchart
2011-12-23 11:35 ` Marek Szyprowski
2011-12-23 11:54 ` Laurent Pinchart
2011-12-23 15:55 ` Sylwester Nawrocki
2011-12-25 21:19 ` Laurent Pinchart
2012-01-02 10:22 ` javier Martin
2012-01-02 11:06 ` Laurent Pinchart [this message]
2012-01-02 11:44 ` javier Martin
2012-01-03 14:00 ` Laurent Pinchart
2011-12-23 11:57 ` Andy Walls
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=201201021206.06397.laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=fabio.estevam@freescale.com \
--cc=hverkuil@xs4all.nl \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=p.osciak@gmail.com \
--cc=r.schwebel@pengutronix.de \
--cc=richard.zhao@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=snjw23@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