From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Nayden Kanchev <nkanchev@mm-sol.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
David Cohen <dacohen@gmail.com>,
Kim HeungJun <riverful@gmail.com>,
andrew.b.adams@gmail.com, Sung Hee Park <shpark7@stanford.edu>
Subject: [RFC v2 0/3] V4L2 API for flash devices and the adp1653 flash controller driver
Date: Tue, 17 May 2011 18:13:12 +0300 [thread overview]
Message-ID: <4DD29088.1060703@maxwell.research.nokia.com> (raw)
Hi,
This patchset implements RFC v4 of V4L2 API for flash devices [1], with
minor modifications, and adds the adp1653 flash controller driver. There
have been changes since v1 [2] of this patchset:
- Faults on the flash LED are allowed to make the LED unusable before
the faults are read. This is implemented in the adp1653 driver.
- Intensities are using standard units; mA for flash / torch and uA for
the indicator.
Thanks to those who have given their feedback so far in the process!
[1] http://www.spinics.net/lists/linux-media/msg32030.html
[2] http://www.spinics.net/lists/linux-media/msg32396.html
Cheers,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next reply other threads:[~2011-05-17 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 15:13 Sakari Ailus [this message]
2011-05-17 15:14 ` [RFC v2 1/3] v4l: Add a class and a set of controls for flash devices Sakari Ailus
2011-05-17 15:14 ` [RFC v2 2/3] v4l: Add flash control documentation Sakari Ailus
2011-05-17 15:14 ` [RFC v2 3/3] adp1653: Add driver for LED flash controller Sakari Ailus
2011-05-18 7:31 ` Laurent Pinchart
2011-05-18 11:29 ` Sakari Ailus
2011-05-18 12:40 ` 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=4DD29088.1060703@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=andrew.b.adams@gmail.com \
--cc=dacohen@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nkanchev@mm-sol.com \
--cc=riverful@gmail.com \
--cc=shpark7@stanford.edu \
/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.