From: Hans Verkuil <hverkuil@xs4all.nl>
To: Daniel Jeong <gshark.jeong@gmail.com>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [RFCv2,1/2] v4l2-controls.h: add addtional Flash fault bits
Date: Tue, 28 Jan 2014 08:04:03 +0100 [thread overview]
Message-ID: <52E75663.1080604@xs4all.nl> (raw)
In-Reply-To: <1390892158-5646-1-git-send-email-gshark.jeong@gmail.com>
On 01/28/2014 07:55 AM, Daniel Jeong wrote:
> Add additional FLASH Fault bits to dectect faults from chip.
> Some Flash drivers support UVLO, IVFM, NTC Trip faults.
> UVLO : Under Voltage Lock Out Threshold crossed
> IVFM : IVFM block reported and/or adjusted LED current Input Voltage Flash Monitor trip threshold
> NTC : NTC Threshold crossed. Many Flash drivers have a pin and the fault bit to
> serves as a threshold detector for negative temperature coefficient (NTC) thermistors.
Please document these new flags as well in Documentation/DocBook/media/v4l/controls.xml.
Regards,
Hans
>
> Signed-off-by: Daniel Jeong <gshark.jeong@gmail.com>
> ---
> include/uapi/linux/v4l2-controls.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/uapi/linux/v4l2-controls.h b/include/uapi/linux/v4l2-controls.h
> index 1666aab..01d730c 100644
> --- a/include/uapi/linux/v4l2-controls.h
> +++ b/include/uapi/linux/v4l2-controls.h
> @@ -803,6 +803,9 @@ enum v4l2_flash_strobe_source {
> #define V4L2_FLASH_FAULT_SHORT_CIRCUIT (1 << 3)
> #define V4L2_FLASH_FAULT_OVER_CURRENT (1 << 4)
> #define V4L2_FLASH_FAULT_INDICATOR (1 << 5)
> +#define V4L2_FLASH_FAULT_UVLO (1 << 6)
> +#define V4L2_FLASH_FAULT_IVFM (1 << 7)
> +#define V4L2_FLASH_FAULT_NTC_TRIP (1 << 8)
>
> #define V4L2_CID_FLASH_CHARGE (V4L2_CID_FLASH_CLASS_BASE + 11)
> #define V4L2_CID_FLASH_READY (V4L2_CID_FLASH_CLASS_BASE + 12)
>
next prev parent reply other threads:[~2014-01-28 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 6:55 [RFCv2,1/2] v4l2-controls.h: add addtional Flash fault bits Daniel Jeong
2014-01-28 6:55 ` [RFCv2,2/2] i2c: add new dual Flash driver,LM3646 Daniel Jeong
2014-01-28 7:12 ` Hans Verkuil
2014-01-29 15:18 ` Sakari Ailus
2014-01-28 7:04 ` Hans Verkuil [this message]
2014-01-28 9:08 ` [RFCv2,1/2] v4l2-controls.h: add addtional Flash fault bits Sakari Ailus
2014-01-28 10:19 ` Daniel Jeong
2014-01-29 15:02 ` 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=52E75663.1080604@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gshark.jeong@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=sakari.ailus@iki.fi \
/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