From: Sylwester Nawrocki <snjw23@gmail.com>
To: jtp.park@samsung.com
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH/RFC 0/2] Support controls at the subdev file handler level
Date: Thu, 10 Mar 2011 20:43:40 +0100 [thread overview]
Message-ID: <4D7929EC.7080003@gmail.com> (raw)
In-Reply-To: <000601cbdf09$76be8c10$643ba430$%park@samsung.com>
Hi,
On 03/10/2011 10:56 AM, Jeongtae Park wrote:
> Hi, all.
>
> Some hardware need to handle per-filehandle level controls.
> Hans suggests add a v4l2_ctrl_handler struct v4l2_fh. It will be work fine.
> Although below patch series are for subdev, but it's great start point.
> I will try to make a patch.
>
> If v4l2 control framework can be handle per-filehandle controls,
> a driver could be handle per-buffer level controls also. (with VB2 callback
> operation)
>
Can you elaborate to what kind of per buffer controls are you referring to?
Using optional meta data planes is expected to be a proper way to do such
things. Either to pass meta data from application to driver or in the opposite
direction.
I can't see how the per buffer controls can be dependent on a per file handle
control support. Perhaps this is only specific to some selected devices.
--
Regards,
Sylwester Nawrocki
next prev parent reply other threads:[~2011-03-10 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 21:27 [PATCH/RFC 0/2] Support controls at the subdev file handler level Laurent Pinchart
2011-03-09 21:27 ` [PATCH/RFC 1/2] v4l: subdev: Move file handle support to drivers Laurent Pinchart
2011-03-09 21:27 ` [PATCH/RFC 2/2] v4l: subdev: Add support for file handler control handler Laurent Pinchart
2011-03-10 9:56 ` [PATCH/RFC 0/2] Support controls at the subdev file handler level Jeongtae Park
2011-03-10 11:22 ` Laurent Pinchart
2011-03-10 19:43 ` Sylwester Nawrocki [this message]
2011-03-11 3:55 ` Jaeryul Oh
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=4D7929EC.7080003@gmail.com \
--to=snjw23@gmail.com \
--cc=jtp.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.