public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kim, HeungJun" <riverful.kim@samsung.com>
To: sungchun.kang@samsung.com
Cc: linux-media@vger.kernel.org,
	"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>
Subject: Re: [PATCH] Add support for M-5MOLS 8 Mega Pixel camera
Date: Tue, 05 Apr 2011 14:36:32 +0900	[thread overview]
Message-ID: <4D9AAA60.4070004@samsung.com> (raw)
In-Reply-To: <007901cbf2c2$bb240bb0$316c2310$%kang@samsung.com>

Hi Sungchun,

The below comments and issues looks the firmware issues.
I add another comments, so you can check this out.

The first plan of this driver I have, is to merge the basic driver code
of M-5MOLS. Because, the M-5MOLS has many variation of versions. It makes
to send the driver to ML or be merged, also respond when the problem issued.

The version considered with version, probably will be the next version.


2011-04-04 오후 9:20, Sungchun Kang 쓴 글:
> Hi heungjun,
> I have tested this version for a few days.
> 
> On 03/16/2011 10:30 PM, Kim, Heungjun wrote:
>> -----Original Message-----
>> From: linux-media-owner@vger.kernel.org [mailto:linux-media-
>> owner@vger.kernel.org] On Behalf Of Kim, Heungjun
>> Sent: Wednesday, March 16, 2011 10:39 PM
>> To: linux-media@vger.kernel.org
>> Cc: hverkuil@xs4all.nl; laurent.pinchart@ideasonboard.com; Kim,
>> Heungjun; Sylwester Nawrocki; Kyungmin Park
>> Subject: [PATCH] Add support for M-5MOLS 8 Mega Pixel camera
>>
>> Add I2C/V4L2 subdev driver for M-5MOLS camera sensor with integrated
>> image signal processor.
>>
>> Signed-off-by: Heungjun Kim <riverful.kim@samsung.com>
>> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>> ---
>>
>> Hi Hans and everyone,
>>
>> This is sixth version of M-5MOLS 8 Mega Pixel camera sensor. And, if
>> you see
>> previous version, you can find at:
>> http://www.spinics.net/lists/linux-media/msg29350.html
>>
>> This driver patch is fixed several times, and the important issues is
>> almost
>> corrected. And, I hope that this is the last version one merged for
>> 2.6.39.
>> I look forward to be reviewed one more time.
>>
>> The summary of this version's feature is belows:
>>
>> 1. Add focus control
>> 	: I've suggest menu type focus control, but I agreed this
>> version is
>> 	not yet the level accepted. So, I did not use focus control
>> which
>> 	I suggest.
>> 	The M-5MOLS focus routine takes some time to execute. But, the
>> user
>> 	application calling v4l2 control, should not hanged while
>> streaming
>> 	using q/dqbuf. So, I use workqueue. I want to discuss the focus
>> 	subject on mailnglist next time.
>>
> 
> I wonder this feature is dependent on this firmware version?
> 
> .....snip
The value can be changable by the firmware, but the usage of focus is not.
The specific mode can be added too. But, it also maintains same usage.

It's scheduled at the next time to consider the version. But, it's hard to
consider all cases.

> 
>> +static int m5mols_start_monitor(struct v4l2_subdev *sd)
>> +{
>> +	struct m5mols_info *info = to_m5mols(sd);
>> +	int ret;
>> +
>> +	ret = m5mols_set_mode(sd, MODE_PARAM);
>> +	if (!ret)
>> +		ret = i2c_w8_param(sd, CAT1_MONITOR_SIZE, info-
>>> res_preset);
>> +	if (!ret)
>> +		ret = i2c_w8_param(sd, CAT1_MONITOR_FPS, info->fps_preset);
>> +	if (!ret)
>> +		ret = m5mols_set_mode(sd, MODE_MONITOR);
>> +	if (!ret && info->do_once) {
>> +		/* After probing the driver, this should be callde once.
>> */
>> +		v4l2_ctrl_handler_setup(&info->handle);
> As test result, When sensor is set monitor mode, if this API is called, 
> Preview data(get from sensor) is craked. Surely, it is good working if this API is called in paramset mode.
> That waw no problem in Version 5. Because it is returned before v4l2_ctrl_handler_init()
> In m5mols_init_controls(version 5) :
> 	ret = i2c_r16_ae(sd, CAT3_MAX_GAIN_MON, (u32 *)&max_ex_mon);
> 	if (ret) 
> 		return ret; // if success, return.
> 
> My test case is :
> S_power->s_fmt->s_stream.
It's a little tricky to control parameter & monitor mode in the M-5MOLS sensor.
Any commands or control is specified that it's available in Docunemt, but
it's just literaly "available", doesn't mean "working well". Especially,
the version difference between firmware is the biggest source of this problems.

Probably, the sensor you have is a different firmware I think.
So If there is any other problem, I recommend to use previous version plz.

If you show me the all version strings, I might help you.

> 
> .....
> BRs Sungchun.
> 
> 

Thanks for comments, and any other issues or opinions, let me know.

Regards,
Heungjun Kim

  reply	other threads:[~2011-04-05  5:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 13:38 [PATCH] Add support for M-5MOLS 8 Mega Pixel camera Kim, Heungjun
2011-03-19 13:37 ` Sylwester Nawrocki
2011-03-19 15:11   ` Kim HeungJun
2011-03-19 19:28     ` Sylwester Nawrocki
2011-03-21  6:08       ` Kim, HeungJun
2011-04-04 12:20 ` Sungchun Kang
2011-04-05  5:36   ` Kim, HeungJun [this message]
2011-04-05  5:38     ` Kim, HeungJun
2011-05-13 10:06 ` [PATCH v7] Add support for M-5MOLS 8 Mega Pixel camera ISP HeungJun, Kim
2011-05-13 11:38   ` HeungJun, Kim
2011-05-16  1:03     ` [PATCH v8] " HeungJun, Kim
2011-05-20  5:56       ` [PATCH v9] " HeungJun, Kim
2011-05-25 13:54         ` Sakari Ailus
2011-05-26  7:12           ` Kim, HeungJun
2011-06-05 11:55             ` Sakari Ailus
2011-06-05 12:11               ` Hans Verkuil
2011-06-05 13:08                 ` Sakari Ailus
2011-06-05 13:13               ` Sylwester Nawrocki
2011-06-06 10:17                 ` Sakari Ailus
2011-06-06  9:14               ` Kim HeungJun
2011-05-27 12:58           ` [PATCH 0/5] Fix micellaneous issues for M-5MOLS driver HeungJun, Kim
2011-05-31  7:35             ` [PATCH v2 0/4] " HeungJun, Kim
2011-05-31  7:35             ` [PATCH v2 1/4] m5mols: Fix capture image size register definition HeungJun, Kim
2011-05-31  7:36             ` [PATCH v2 2/4] m5mols: add m5mols_read_u8/u16/u32() according to I2C byte width HeungJun, Kim
2011-05-31  7:36             ` [PATCH v2 3/4] m5mols: remove union in the m5mols_get_version(), and VERSION_SIZE HeungJun, Kim
2011-06-05 12:03               ` Sakari Ailus
2011-06-05 12:11                 ` Sakari Ailus
2011-06-06  9:20                   ` Kim HeungJun
2011-05-31  7:36             ` [PATCH v2 4/4] m5mols: add parenthesis <> for the head and back of email address HeungJun, Kim
2011-05-27 12:58           ` [PATCH 1/5] m5mols: fix reading wrong size of captured main/thumb image HeungJun, Kim
2011-05-27 12:58           ` [PATCH 2/5] m5mols: add m5mols_read_u8/u16/u32() according to I2C byte width HeungJun, Kim
2011-05-27 12:58           ` [PATCH 3/5] m5mols: remove union in the m5mols_get_version(), and VERSION_SIZE HeungJun, Kim
2011-05-27 12:58           ` [PATCH 4/5] m5mols: rename m5mols_capture_error_handler() to proper name HeungJun, Kim
2011-05-27 12:58           ` [PATCH 5/5] m5mols: add parenthesis <> for the head and back of email address HeungJun, Kim

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=4D9AAA60.4070004@samsung.com \
    --to=riverful.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sungchun.kang@samsung.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