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: Re: [RFC 0/3] V4L2 API for flash devices and the adp1653 flash controller driver
Date: Mon, 16 May 2011 19:48:57 +0300 [thread overview]
Message-ID: <4DD15579.2080005@maxwell.research.nokia.com> (raw)
In-Reply-To: <4DD11FEC.8050308@maxwell.research.nokia.com>
Sakari Ailus wrote:
> Hi,
>
> This is a patchset which implements RFC v4 of V4L2 API for flash devices
> [1], with minor modifications, and adds the adp1653 flash controller driver.
Replying to myself, the associated board code for the N900 isn't part of
this patchset. It's are available here with the rest of the drivers:
<URL:https://www.gitorious.org/omap3camera/pages/Home>
My current intention is to fix the board code in the future with the
rest of the drivers as I don't see very much use for the flash driver
before the et8ek8 image sensor driver.
The patches in the patchset itself are in the rx51-002-upstream branch.
Regards,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
prev parent reply other threads:[~2011-05-16 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 13:00 [RFC 0/3] V4L2 API for flash devices and the adp1653 flash controller driver Sakari Ailus
2011-05-16 13:00 ` [PATCH 1/3] v4l: Add a class and a set of controls for flash devices Sakari Ailus
2011-05-16 13:00 ` [PATCH 2/3] v4l: Add flash control documentation Sakari Ailus
2011-05-16 13:00 ` [PATCH 3/3] adp1653: Add driver for LED flash controller Sakari Ailus
2011-05-16 20:31 ` Laurent Pinchart
2011-05-17 5:38 ` Sakari Ailus
2011-05-17 7:23 ` Laurent Pinchart
2011-05-17 10:47 ` Sakari Ailus
2011-05-17 10:51 ` Laurent Pinchart
2011-06-09 15:10 ` Laurent Pinchart
2011-06-10 8:20 ` Sakari Ailus
2011-05-16 16:48 ` Sakari Ailus [this message]
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=4DD15579.2080005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox