From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Andy Walls <awalls@radix.net>
Cc: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
hverkuil@xs4all.nl,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Chroma gain configuration
Date: Mon, 22 Feb 2010 09:15:04 -0300 [thread overview]
Message-ID: <4B827548.10005@redhat.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,
>
> 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?
>
> I'd like to implement specific "technician controls", something an
> average user wouldn't use, for a few subdevs.
The exposition of a control to the user or not is a decision of the userspace
software developer. We shouldn't be too concerned about it. Eventually,
we can group some controls on a "raw hardware level" group. I don't think we
need a media controller for it. Also, this won't avoid developers to use the media
controller to expose such controls to userspace.
>> I see there is an existing boolean control called V4L2_CID_CHROMA_AGC,
>> which would be the logical candidate for allowing the user to disable
>> the chroma AGC. However, once this is done I still need to expose the
>> ability to set the gain manually (bits 6-0 of register 0x0f).
>>
>> Is there some existing control I am just missing? Or do I need to do
>> this through a private control.
>>
>> I'm asking because it seems a bit strange that someone would introduce
>> a v4l2 standard control to disable the AGC but not have the ability to
>> manually set the gain once it was disabled.
>
> Devin,
>
> Well, I can imagine letting hardware do the initial AGC, and then when
> it is settled manually disabling it to prevent hardware from getting
> "fooled".
I did some tests on it with cx23881/cx23883 chips. At least on cx88, as far
as I remember, the AGC doesn't affect the saturation register, so, this
trick won't work.
The issue with cx88 chips is that, with some video input sources, the
AGC over-saturates the color pattern. So, depending on the analog video
standard and the quality of the source (TV or Composite/Svideo), it gives
more reallistic colors with different AGC/saturation configuration.
Cheers,
Mauro
next prev parent reply other threads:[~2010-02-22 12:16 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 [this message]
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
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=4B827548.10005@redhat.com \
--to=mchehab@redhat.com \
--cc=awalls@radix.net \
--cc=dheitmueller@kernellabs.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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