From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: David Cohen <dacohen@gmail.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Nayden Kanchev <nkanchev@mm-sol.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Cohen David Abraham <david.cohen@nokia.com>
Subject: Re: [RFC] V4L2 API for flash devices
Date: Wed, 06 Apr 2011 11:04:20 +0300 [thread overview]
Message-ID: <4D9C1E84.60606@maxwell.research.nokia.com> (raw)
In-Reply-To: <BANLkTik9vSSRKYHj9cUGUzxFy_cpcVo7ZQ@mail.gmail.com>
David Cohen wrote:
> On Mon, Mar 28, 2011 at 3:55 PM, Sakari Ailus
> <sakari.ailus@maxwell.research.nokia.com> wrote:
>> Hi,
>
> Hi Sakari,
Thanks for the comments, David!
> [snip]
>
>> This is a bitmask containing the fault information for the flash. This
>> assumes the proposed V4L2 bit mask controls [5]; otherwise this would
>> likely need to be a set of controls.
>>
>> #define V4L2_FLASH_FAULT_OVER_VOLTAGE 0x00000001
>> #define V4L2_FLASH_FAULT_TIMEOUT 0x00000002
>> #define V4L2_FLASH_FAULT_OVER_TEMPERATURE 0x00000004
>> #define V4L2_FLASH_FAULT_SHORT_CIRCUIT 0x00000008
>
> Sorry for bringing this a bit late. As we already talked directly,
> IMO (1 << 0), (1 << 1), ... could have a better readability to expose
> how you want to define an expand these macros.
I'll change this to the next version of the RFC.
Regards,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next prev parent reply other threads:[~2011-04-06 8:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 12:55 [RFC] V4L2 API for flash devices Sakari Ailus
2011-03-29 6:49 ` Hans Verkuil
2011-03-29 9:35 ` Sakari Ailus
2011-03-29 9:54 ` Hans Verkuil
2011-03-29 11:38 ` Sakari Ailus
2011-03-29 11:51 ` Sakari Ailus
2011-03-30 8:47 ` Laurent Pinchart
2011-04-05 10:00 ` Sakari Ailus
2011-05-02 16:04 ` Sakari Ailus
2011-05-02 19:13 ` Hans Verkuil
2011-05-02 19:32 ` Laurent Pinchart
2011-05-02 20:07 ` Hans Verkuil
2011-03-30 8:55 ` Laurent Pinchart
2011-03-30 12:44 ` Sakari Ailus
2011-03-30 13:53 ` Laurent Pinchart
2011-03-30 14:18 ` Sakari Ailus
2011-03-30 14:57 ` David Cohen
2011-03-30 15:00 ` Laurent Pinchart
2011-03-31 8:09 ` Sakari Ailus
2011-03-29 10:43 ` Kim, HeungJun
2011-03-29 14:41 ` Sakari Ailus
2011-03-30 5:06 ` Kim, HeungJun
2011-03-30 11:37 ` Sakari Ailus
2011-03-30 20:37 ` Kim HeungJun
2011-03-31 8:50 ` Sakari Ailus
2011-03-30 9:34 ` Laurent Pinchart
2011-03-30 11:05 ` Sakari Ailus
2011-03-30 13:54 ` Laurent Pinchart
2011-03-31 8:17 ` Sakari Ailus
2011-04-05 10:23 ` Sakari Ailus
2011-04-05 10:39 ` Laurent Pinchart
2011-04-05 11:21 ` Sakari Ailus
2011-04-05 11:28 ` Laurent Pinchart
2011-04-05 13:35 ` Sakari Ailus
[not found] ` <4D9B303D.1000003@mm-sol.com>
2011-04-05 16:25 ` Laurent Pinchart
2011-04-05 12:11 ` David Cohen
2011-04-06 8:04 ` Sakari Ailus [this message]
2011-04-12 19:31 ` Sung Hee Park
[not found] ` <BANLkTik+xqCD7uiGUchsehoUy+gwM+Cjdg@mail.gmail.com>
2011-04-13 12:16 ` Sakari Ailus
2011-04-14 19:38 ` Laurent Pinchart
2011-04-15 5:27 ` 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=4D9C1E84.60606@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=dacohen@gmail.com \
--cc=david.cohen@nokia.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 \
/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