From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Andy Walls <awalls@radix.net>
Cc: hverkuil@xs4all.nl,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: Chroma gain configuration
Date: Tue, 23 Feb 2010 01:50:33 +0200 [thread overview]
Message-ID: <4B831849.3090701@maxwell.research.nokia.com> (raw)
In-Reply-To: <1266838852.3095.20.camel@palomino.walls.org>
Andy Walls wrote:
> On Sun, 2010-02-21 at 23:07 -0500, Devin Heitmueller wrote:
>> I am doing some work on the saa711x driver, and ran into a case where
>> I need to disable the chroma AGC and manually set the chroma gain.
>
> Sakari, Hans, or anyone else,
Hi Andy,
> On a somewhat related note, what is the status of the media controller
> and of file handles per v4l2_subdev. Will Sakari's V4L file-handle
> changes be all we need for the infrastructure or is there more to be
> done after that?
There are three things:
- V4L2 file handles (and events)
- V4L2 subdev device nodes
- Media controller
The file handles and events appear to be fairly ready.
> I'd like to implement specific "technician controls", something an
> average user wouldn't use, for a few subdevs.
For that you'd need at least V4L2 subdev device nodes, preferrably also
Media controller e.g. for the user space to know the two devices indeed
are connected to the same higher level device. File handles do not
matter here; it's just a generic way to store file handle specific data,
required by events, for example.
Subdev device nodes and Media controller patches live in Laurent's tree
at linuxtv.org at the moment.
Regards,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
prev parent reply other threads:[~2010-02-22 23:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 4:07 Chroma gain configuration Devin Heitmueller
2010-02-22 11:04 ` Frej Drejhammar
2010-02-22 11:40 ` Andy Walls
2010-02-22 12:15 ` Mauro Carvalho Chehab
2010-02-22 13:10 ` Devin Heitmueller
2010-02-22 13:40 ` Mauro Carvalho Chehab
2010-02-22 13:47 ` Devin Heitmueller
2010-02-22 13:58 ` Mauro Carvalho Chehab
2010-02-22 21:17 ` Devin Heitmueller
2010-02-22 21:32 ` Mauro Carvalho Chehab
2010-02-22 21:38 ` Devin Heitmueller
2010-02-22 21:47 ` Hans Verkuil
2010-02-22 21:41 ` Hans Verkuil
2010-02-22 21:43 ` Devin Heitmueller
2010-02-22 21:54 ` Hans Verkuil
2010-02-22 22:00 ` Devin Heitmueller
2010-02-23 7:53 ` Hans Verkuil
2010-02-23 14:20 ` Andy Walls
2010-02-23 14:41 ` Hans Verkuil
2010-02-23 15:33 ` Andy Walls
2010-02-23 15:41 ` Andy Walls
2010-02-23 18:11 ` My TV's standard video controls (Re: Chroma gain configuration) Andy Walls
2010-02-23 15:15 ` Chroma gain configuration Devin Heitmueller
2010-02-25 4:39 ` Devin Heitmueller
2010-02-22 23:50 ` Sakari Ailus [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=4B831849.3090701@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=awalls@radix.net \
--cc=dheitmueller@kernellabs.com \
--cc=hverkuil@xs4all.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox