All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, s.nawrocki@samsung.com,
	hechtb@googlemail.com, g.liakhovetski@gmx.de
Subject: [RFC] New class for low level sensors controls?
Date: Tue, 6 Sep 2011 14:36:53 +0300	[thread overview]
Message-ID: <20110906113653.GF1393@valkosipuli.localdomain> (raw)

Hi all,

We are beginning to have raw bayer image sensor drivers in the mainline.
Typically such sensors are not controlled by general purpose applications
but e.g. require a camera control algorithm framework in user space. This
needs to be implemented in libv4l for general purpose applications to work
properly on this kind of hardware.

These sensors expose controls such as

- Per-component gain controls. Red, blue, green (blue) and green (red)
  gains.

- Link frequency. The frequency of the data link from the sensor to the
  bridge.

- Horizontal and vertical blanking.

None of these controls are suitable for use of general purpose applications
(let alone the end user!) but for the camera control algorithms.

We have a control class called V4L2_CTRL_CLASS_CAMERA for camera controls.
However, the controls in this class are relatively high level controls which
are suitable for end user. The algorithms in the libv4l or a webcam could
implement many of these controls whereas I see that only
V4L2_CID_EXPOSURE_ABSOLUTE might be implemented by raw bayer sensors.

My question is: would it make sense to create a new class of controls for
the low level sensor controls in a similar fashion we have a control class
for the flash controls?

-- 
Sakari Ailus
e-mail: sakari.ailus@iki.fi	jabber/XMPP/Gmail: sailus@retiisi.org.uk

             reply	other threads:[~2011-09-06 11:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 11:36 Sakari Ailus [this message]
2011-09-06 11:41 ` [RFC] New class for low level sensors controls? Laurent Pinchart
2011-09-06 12:22   ` Sakari Ailus
2011-09-08  9:51     ` Laurent Pinchart
2011-09-08 10:40       ` Sakari Ailus
2011-09-08 11:24     ` Subash Patel
2011-09-08 11:44       ` Sakari Ailus
2011-09-13 10:33         ` Laurent Pinchart
2011-09-13 12:00           ` Sakari Ailus
2011-09-13 13:12             ` Laurent Pinchart
2011-09-08 12:35     ` Guennadi Liakhovetski
2011-09-08 13:21       ` Sakari Ailus
2011-09-08 13:43         ` Guennadi Liakhovetski
2011-09-13 10:31       ` Laurent Pinchart
2011-09-13 14:26         ` Guennadi Liakhovetski
2011-09-26  9:51 ` Hans Verkuil
2011-09-26  9:54   ` Laurent Pinchart

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=20110906113653.GF1393@valkosipuli.localdomain \
    --to=sakari.ailus@iki.fi \
    --cc=g.liakhovetski@gmx.de \
    --cc=hechtb@googlemail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=s.nawrocki@samsung.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 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.