public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Andy Walls <awalls@radix.net>,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
	hverkuil@xs4all.nl,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Chroma gain configuration
Date: Mon, 22 Feb 2010 10:58:52 -0300	[thread overview]
Message-ID: <4B828D9C.50303@redhat.com> (raw)
In-Reply-To: <829197381002220547n3468019bmdb17f401f7c5b6e1@mail.gmail.com>

Devin Heitmueller wrote:
> On Mon, Feb 22, 2010 at 8:40 AM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> I think that the control you want is V4L2_CID_GAIN.
> 
> I would have guessed the CID_GAIN control would have been responsible
> for *luma* gain.  I could be wrong about that of course (but that is
> what I believe people typically think of when they think of "gain" in
> general).

Maybe it is for luma, but I bet that this is also is used for more than one
different kind of control. We should revisit those controls and properly
specify what they should do.
> 
>>> I believe there probably are cases where extended controls are required,
>>> but I believe just a general user control based on
>>> V4L2_CID_PRIVATE_BASE should probably be able to work even with the
>>> generic VIDIOC_S_CTRL
>>>
>>> I'm just asking because it would mean in order for v4l2-dbg to work
>>> with my solution i would have to add support for extended controls in
>>> general to the saa7115 driver, which shouldn't be necessary.
>> The end objective is to have everybody implementing extended controls and
>> removing the old controls, letting the V4L2 ioctl2 to convert a call to a
>> simple control into an extended control callback. So, I think it would
>> be worthy to implement extended control on saa7115.
> 
> Ok then.  I'll add the 15-20 lines of code which add the extended
> controls mechanism to the 7115, which just operates as a passthrough
> for the older control interface.

The better is to do the opposite: extended being the control interface and
the old calls as a passthrough, since the idea is to remove the old interface
after having all drivers converted.

-- 

Cheers,
Mauro

  reply	other threads:[~2010-02-22 13:59 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 [this message]
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=4B828D9C.50303@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