From: Hans Verkuil <hverkuil@xs4all.nl>
To: vkalia@codeaurora.org
Cc: linux-media@vger.kernel.org
Subject: Re: User data propagation for video codecs
Date: Sat, 14 Sep 2013 05:22:41 +0200 [thread overview]
Message-ID: <5233D681.4000802@xs4all.nl> (raw)
In-Reply-To: <79eef80b5fa29d83a7ae9a3f7d83cea8.squirrel@www.codeaurora.org>
On 09/13/2013 11:54 PM, vkalia@codeaurora.org wrote:
> Hi
>
> For video decoder, our video driver, which is V4l2 based, exposes two
> capabilities:
>
> 1. V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE for transaction of compressed buffers.
> 2. V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE for transaction of
> decoded/uncompressed buffers.
>
> We have a requirement to propagate "user specific data" from compressed
> buffer to uncompressed buffer. We are not able to find any field in
> "struct v4l2_buffer" which can be used for this purpose. Please suggest if
> this can be achieved with current V4L2 framework.
It depends how the user data is organized. If it is situated right
before the actual data, then the data_offset field of v4l2_plane can be
used. If it is an independent piece of data, then you can pass it on in
an additional plane.
Regards,
Hans
prev parent reply other threads:[~2013-09-14 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 21:54 User data propagation for video codecs vkalia
2013-09-14 3:22 ` Hans Verkuil [this message]
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=5233D681.4000802@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=vkalia@codeaurora.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