linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
	sylvester.nawrocki@gmail.com
Subject: [PATCH 0/3] OV9650/52 image sensor subdev driver
Date: Sat, 19 Jan 2013 22:27:19 +0100	[thread overview]
Message-ID: <1358630842-12689-1-git-send-email-sylvester.nawrocki@gmail.com> (raw)

This patch series adds a v4l2 subdev driver for Omnivision OV9650/52
image sensors, a helper function at the v4l2 control framework
allowing to modify range of a control and a header file including
definitions of standard image resolutions.

I've tested the ctrl helper function with the OV9650 driver and
a modified v4l2-ctl.

Changes at the sensor driver since the first version include:
 - removed the exposure reference area and gain ceiling private
   controls and control auto cluster used for gain/auto_gain,
   auto/manual exposure controls;
 - v4l2_ctrl_handler_setup() used instead of a function setting
   initial control's values in H/W explicitly;
 - added event subscribe/unsubscribe ioctl handlers so v4l2 events
   are supported at the subdev node;
 - v4l2_ctrl_modify_range() function is now used to modify the
   exposure time control's range when output format/frame rate
   is modified, rather than updating the range manually in the
   driver, without any notification to user space;
 - added description of the platform data structure;
 - removed the contrast control stubs.

Sylwester Nawrocki (3):
  [media] Add header file defining standard image sizes
  v4l2-ctrl: Add helper function for control range update
  V4L: Add driver for OV9650/52 image sensors

 Documentation/DocBook/media/v4l/vidioc-dqevent.xml |    6 +
 drivers/media/i2c/Kconfig                          |    7 +
 drivers/media/i2c/Makefile                         |    1 +
 drivers/media/i2c/ov9650.c                         | 1582 ++++++++++++++++++++
 drivers/media/v4l2-core/v4l2-ctrls.c               |  142 ++-
 include/media/image-sizes.h                        |   34 +
 include/media/ov9650.h                             |   27 +
 include/media/v4l2-ctrls.h                         |   20 +
 include/uapi/linux/videodev2.h                     |    1 +
 9 files changed, 1781 insertions(+), 39 deletions(-)
 create mode 100644 drivers/media/i2c/ov9650.c
 create mode 100644 include/media/image-sizes.h
 create mode 100644 include/media/ov9650.h

--
1.7.4.1


             reply	other threads:[~2013-01-19 21:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 21:27 Sylwester Nawrocki [this message]
2013-01-19 21:27 ` [PATCH 1/3] [media] Add header file defining standard image sizes Sylwester Nawrocki
2013-01-21  9:01   ` Hans Verkuil
2013-01-22 21:42     ` Sylwester Nawrocki
2013-01-19 21:27 ` [PATCH 2/3] v4l2-ctrl: Add helper function for control range update Sylwester Nawrocki
2013-01-21  8:25   ` Hans Verkuil
2013-01-22 21:41     ` Sylwester Nawrocki
2013-01-19 21:27 ` [PATCH 3/3] V4L: Add driver for OV9650/52 image sensors Sylwester Nawrocki
2013-01-21  9:34   ` Hans Verkuil
2013-01-22 21:57     ` Sylwester Nawrocki

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=1358630842-12689-1-git-send-email-sylvester.nawrocki@gmail.com \
    --to=sylvester.nawrocki@gmail.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;
as well as URLs for NNTP newsgroup(s).