2009-06-29 15:41:26 +07:00
|
|
|
/*
|
|
|
|
* mt9v011 -Micron 1/4-Inch VGA Digital Image Sensor
|
|
|
|
*
|
2014-02-07 17:03:07 +07:00
|
|
|
* Copyright (c) 2009 Mauro Carvalho Chehab
|
2009-06-29 15:41:26 +07:00
|
|
|
* This code is placed under the terms of the GNU General Public License v2
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/i2c.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 15:04:11 +07:00
|
|
|
#include <linux/slab.h>
|
2009-06-29 15:41:26 +07:00
|
|
|
#include <linux/videodev2.h>
|
|
|
|
#include <linux/delay.h>
|
2011-07-04 01:03:12 +07:00
|
|
|
#include <linux/module.h>
|
2009-07-14 12:38:18 +07:00
|
|
|
#include <asm/div64.h>
|
2009-06-29 15:41:26 +07:00
|
|
|
#include <media/v4l2-device.h>
|
2012-09-07 15:42:15 +07:00
|
|
|
#include <media/v4l2-ctrls.h>
|
2011-01-08 17:08:02 +07:00
|
|
|
#include <media/mt9v011.h>
|
2009-06-29 15:41:26 +07:00
|
|
|
|
|
|
|
MODULE_DESCRIPTION("Micron mt9v011 sensor driver");
|
2014-02-07 17:03:07 +07:00
|
|
|
MODULE_AUTHOR("Mauro Carvalho Chehab");
|
2009-06-29 15:41:26 +07:00
|
|
|
MODULE_LICENSE("GPL");
|
|
|
|
|
|
|
|
static int debug;
|
|
|
|
module_param(debug, int, 0);
|
|
|
|
MODULE_PARM_DESC(debug, "Debug level (0-2)");
|
|
|
|
|
2011-01-08 17:08:02 +07:00
|
|
|
#define R00_MT9V011_CHIP_VERSION 0x00
|
|
|
|
#define R01_MT9V011_ROWSTART 0x01
|
|
|
|
#define R02_MT9V011_COLSTART 0x02
|
|
|
|
#define R03_MT9V011_HEIGHT 0x03
|
|
|
|
#define R04_MT9V011_WIDTH 0x04
|
|
|
|
#define R05_MT9V011_HBLANK 0x05
|
|
|
|
#define R06_MT9V011_VBLANK 0x06
|
|
|
|
#define R07_MT9V011_OUT_CTRL 0x07
|
|
|
|
#define R09_MT9V011_SHUTTER_WIDTH 0x09
|
|
|
|
#define R0A_MT9V011_CLK_SPEED 0x0a
|
|
|
|
#define R0B_MT9V011_RESTART 0x0b
|
|
|
|
#define R0C_MT9V011_SHUTTER_DELAY 0x0c
|
|
|
|
#define R0D_MT9V011_RESET 0x0d
|
|
|
|
#define R1E_MT9V011_DIGITAL_ZOOM 0x1e
|
|
|
|
#define R20_MT9V011_READ_MODE 0x20
|
|
|
|
#define R2B_MT9V011_GREEN_1_GAIN 0x2b
|
|
|
|
#define R2C_MT9V011_BLUE_GAIN 0x2c
|
|
|
|
#define R2D_MT9V011_RED_GAIN 0x2d
|
|
|
|
#define R2E_MT9V011_GREEN_2_GAIN 0x2e
|
|
|
|
#define R35_MT9V011_GLOBAL_GAIN 0x35
|
|
|
|
#define RF1_MT9V011_CHIP_ENABLE 0xf1
|
|
|
|
|
|
|
|
#define MT9V011_VERSION 0x8232
|
|
|
|
#define MT9V011_REV_B_VERSION 0x8243
|
|
|
|
|
2009-06-29 15:41:26 +07:00
|
|
|
struct mt9v011 {
|
|
|
|
struct v4l2_subdev sd;
|
2012-09-07 15:42:15 +07:00
|
|
|
struct v4l2_ctrl_handler ctrls;
|
2009-07-04 18:03:48 +07:00
|
|
|
unsigned width, height;
|
2009-07-14 12:38:18 +07:00
|
|
|
unsigned xtal;
|
2009-08-07 11:09:54 +07:00
|
|
|
unsigned hflip:1;
|
|
|
|
unsigned vflip:1;
|
2009-06-29 15:41:26 +07:00
|
|
|
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
u16 global_gain, exposure;
|
|
|
|
s16 red_bal, blue_bal;
|
2009-06-29 15:41:26 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
static inline struct mt9v011 *to_mt9v011(struct v4l2_subdev *sd)
|
|
|
|
{
|
|
|
|
return container_of(sd, struct mt9v011, sd);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mt9v011_read(struct v4l2_subdev *sd, unsigned char addr)
|
|
|
|
{
|
|
|
|
struct i2c_client *c = v4l2_get_subdevdata(sd);
|
|
|
|
__be16 buffer;
|
|
|
|
int rc, val;
|
|
|
|
|
2009-06-29 21:12:05 +07:00
|
|
|
rc = i2c_master_send(c, &addr, 1);
|
|
|
|
if (rc != 1)
|
2009-06-29 15:41:26 +07:00
|
|
|
v4l2_dbg(0, debug, sd,
|
|
|
|
"i2c i/o error: rc == %d (should be 1)\n", rc);
|
|
|
|
|
|
|
|
msleep(10);
|
|
|
|
|
2009-06-29 21:12:05 +07:00
|
|
|
rc = i2c_master_recv(c, (char *)&buffer, 2);
|
|
|
|
if (rc != 2)
|
2009-06-29 15:41:26 +07:00
|
|
|
v4l2_dbg(0, debug, sd,
|
2009-06-29 21:12:05 +07:00
|
|
|
"i2c i/o error: rc == %d (should be 2)\n", rc);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
|
|
|
val = be16_to_cpu(buffer);
|
|
|
|
|
|
|
|
v4l2_dbg(2, debug, sd, "mt9v011: read 0x%02x = 0x%04x\n", addr, val);
|
|
|
|
|
|
|
|
return val;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void mt9v011_write(struct v4l2_subdev *sd, unsigned char addr,
|
|
|
|
u16 value)
|
|
|
|
{
|
|
|
|
struct i2c_client *c = v4l2_get_subdevdata(sd);
|
|
|
|
unsigned char buffer[3];
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
buffer[0] = addr;
|
|
|
|
buffer[1] = value >> 8;
|
|
|
|
buffer[2] = value & 0xff;
|
|
|
|
|
|
|
|
v4l2_dbg(2, debug, sd,
|
|
|
|
"mt9v011: writing 0x%02x 0x%04x\n", buffer[0], value);
|
2009-07-04 18:03:48 +07:00
|
|
|
rc = i2c_master_send(c, buffer, 3);
|
2009-06-29 21:12:05 +07:00
|
|
|
if (rc != 3)
|
2009-06-29 15:41:26 +07:00
|
|
|
v4l2_dbg(0, debug, sd,
|
|
|
|
"i2c i/o error: rc == %d (should be 3)\n", rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
struct i2c_reg_value {
|
|
|
|
unsigned char reg;
|
|
|
|
u16 value;
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Values used at the original driver
|
|
|
|
* Some values are marked as Reserved at the datasheet
|
|
|
|
*/
|
|
|
|
static const struct i2c_reg_value mt9v011_init_default[] = {
|
|
|
|
{ R0D_MT9V011_RESET, 0x0001 },
|
|
|
|
{ R0D_MT9V011_RESET, 0x0000 },
|
2009-06-29 21:03:22 +07:00
|
|
|
|
|
|
|
{ R0C_MT9V011_SHUTTER_DELAY, 0x0000 },
|
2009-07-04 18:15:11 +07:00
|
|
|
{ R09_MT9V011_SHUTTER_WIDTH, 0x1fc },
|
|
|
|
|
|
|
|
{ R0A_MT9V011_CLK_SPEED, 0x0000 },
|
2009-06-29 21:03:22 +07:00
|
|
|
{ R1E_MT9V011_DIGITAL_ZOOM, 0x0000 },
|
|
|
|
|
2009-07-14 12:38:18 +07:00
|
|
|
{ R07_MT9V011_OUT_CTRL, 0x0002 }, /* chip enable */
|
2009-06-29 15:41:26 +07:00
|
|
|
};
|
|
|
|
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
|
|
|
|
static u16 calc_mt9v011_gain(s16 lineargain)
|
|
|
|
{
|
|
|
|
|
|
|
|
u16 digitalgain = 0;
|
|
|
|
u16 analogmult = 0;
|
|
|
|
u16 analoginit = 0;
|
|
|
|
|
|
|
|
if (lineargain < 0)
|
|
|
|
lineargain = 0;
|
|
|
|
|
|
|
|
/* recommended minimum */
|
|
|
|
lineargain += 0x0020;
|
|
|
|
|
|
|
|
if (lineargain > 2047)
|
|
|
|
lineargain = 2047;
|
|
|
|
|
|
|
|
if (lineargain > 1023) {
|
|
|
|
digitalgain = 3;
|
|
|
|
analogmult = 3;
|
|
|
|
analoginit = lineargain / 16;
|
|
|
|
} else if (lineargain > 511) {
|
|
|
|
digitalgain = 1;
|
|
|
|
analogmult = 3;
|
|
|
|
analoginit = lineargain / 8;
|
|
|
|
} else if (lineargain > 255) {
|
|
|
|
analogmult = 3;
|
|
|
|
analoginit = lineargain / 4;
|
|
|
|
} else if (lineargain > 127) {
|
|
|
|
analogmult = 1;
|
|
|
|
analoginit = lineargain / 2;
|
|
|
|
} else
|
|
|
|
analoginit = lineargain;
|
|
|
|
|
|
|
|
return analoginit + (analogmult << 7) + (digitalgain << 9);
|
|
|
|
|
|
|
|
}
|
|
|
|
|
2009-06-29 15:41:26 +07:00
|
|
|
static void set_balance(struct v4l2_subdev *sd)
|
|
|
|
{
|
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
u16 green_gain, blue_gain, red_gain;
|
2011-06-02 22:43:14 +07:00
|
|
|
u16 exposure;
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
s16 bal;
|
2011-06-02 22:43:14 +07:00
|
|
|
|
|
|
|
exposure = core->exposure;
|
2009-06-29 15:41:26 +07:00
|
|
|
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
green_gain = calc_mt9v011_gain(core->global_gain);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
bal = core->global_gain;
|
|
|
|
bal += (core->blue_bal * core->global_gain / (1 << 7));
|
|
|
|
blue_gain = calc_mt9v011_gain(bal);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
bal = core->global_gain;
|
|
|
|
bal += (core->red_bal * core->global_gain / (1 << 7));
|
|
|
|
red_gain = calc_mt9v011_gain(bal);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
[media] mt9v011: Fixed gain calculation
The implementation of the gain calculation for this sensor is incorrect.
It is only working for the first 127 values.
The reason is, that the gain cannot be set directly by writing a value
into the gain registers of the sensor. The gain register work this way
(see datasheet page 24): bits 0 to 6 are called "initial gain". These
are linear. But bits 7 and 8 ("analog multiplicative factors") and bits
9 and 10 ("digital multiplicative factors") work completely different:
Each of these bits increase the gain by the factor 2. So if the bits
7-10 are 0011, 0110, 1100 or 0101 for example, the gain from bits 0-6 is
multiplied by 4. The order of the bits 7-10 is not important for the
resulting gain. (But there are some recommended values for low noise)
The current driver doesn't do this correctly: If the current gain is 000
0111 1111 (127) and the gain is increased by 1, you would expect the
image to become brighter. But the image is completly dark, because the
new gain is 000 1000 0000 (128). This means: Initial gain of 0,
multiplied by 2. The result is 0.
This patch adds a new function which does the gain calculation and also
fixes the same bug for red_balance and blue_balance. Additionally, the
driver follows the recommendation from the datasheet, which says, that
the gain should always be above 0x0020.
Tested-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Johannes Obermaier <johannes.obermaier@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-06-02 23:03:41 +07:00
|
|
|
mt9v011_write(sd, R2B_MT9V011_GREEN_1_GAIN, green_gain);
|
|
|
|
mt9v011_write(sd, R2E_MT9V011_GREEN_2_GAIN, green_gain);
|
2009-06-29 15:41:26 +07:00
|
|
|
mt9v011_write(sd, R2C_MT9V011_BLUE_GAIN, blue_gain);
|
|
|
|
mt9v011_write(sd, R2D_MT9V011_RED_GAIN, red_gain);
|
2011-06-02 22:43:14 +07:00
|
|
|
mt9v011_write(sd, R09_MT9V011_SHUTTER_WIDTH, exposure);
|
2009-06-29 15:41:26 +07:00
|
|
|
}
|
|
|
|
|
2009-08-07 07:03:35 +07:00
|
|
|
static void calc_fps(struct v4l2_subdev *sd, u32 *numerator, u32 *denominator)
|
2009-07-14 12:38:18 +07:00
|
|
|
{
|
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
|
|
|
unsigned height, width, hblank, vblank, speed;
|
|
|
|
unsigned row_time, t_time;
|
|
|
|
u64 frames_per_ms;
|
|
|
|
unsigned tmp;
|
|
|
|
|
|
|
|
height = mt9v011_read(sd, R03_MT9V011_HEIGHT);
|
|
|
|
width = mt9v011_read(sd, R04_MT9V011_WIDTH);
|
|
|
|
hblank = mt9v011_read(sd, R05_MT9V011_HBLANK);
|
|
|
|
vblank = mt9v011_read(sd, R06_MT9V011_VBLANK);
|
|
|
|
speed = mt9v011_read(sd, R0A_MT9V011_CLK_SPEED);
|
|
|
|
|
|
|
|
row_time = (width + 113 + hblank) * (speed + 2);
|
|
|
|
t_time = row_time * (height + vblank + 1);
|
|
|
|
|
|
|
|
frames_per_ms = core->xtal * 1000l;
|
|
|
|
do_div(frames_per_ms, t_time);
|
|
|
|
tmp = frames_per_ms;
|
|
|
|
|
|
|
|
v4l2_dbg(1, debug, sd, "Programmed to %u.%03u fps (%d pixel clcks)\n",
|
|
|
|
tmp / 1000, tmp % 1000, t_time);
|
2009-08-07 07:03:35 +07:00
|
|
|
|
|
|
|
if (numerator && denominator) {
|
|
|
|
*numerator = 1000;
|
|
|
|
*denominator = (u32)frames_per_ms;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static u16 calc_speed(struct v4l2_subdev *sd, u32 numerator, u32 denominator)
|
|
|
|
{
|
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
|
|
|
unsigned height, width, hblank, vblank;
|
|
|
|
unsigned row_time, line_time;
|
|
|
|
u64 t_time, speed;
|
|
|
|
|
|
|
|
/* Avoid bogus calculus */
|
|
|
|
if (!numerator || !denominator)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
height = mt9v011_read(sd, R03_MT9V011_HEIGHT);
|
|
|
|
width = mt9v011_read(sd, R04_MT9V011_WIDTH);
|
|
|
|
hblank = mt9v011_read(sd, R05_MT9V011_HBLANK);
|
|
|
|
vblank = mt9v011_read(sd, R06_MT9V011_VBLANK);
|
|
|
|
|
|
|
|
row_time = width + 113 + hblank;
|
|
|
|
line_time = height + vblank + 1;
|
|
|
|
|
|
|
|
t_time = core->xtal * ((u64)numerator);
|
|
|
|
/* round to the closest value */
|
|
|
|
t_time += denominator / 2;
|
|
|
|
do_div(t_time, denominator);
|
|
|
|
|
|
|
|
speed = t_time;
|
|
|
|
do_div(speed, row_time * line_time);
|
|
|
|
|
|
|
|
/* Avoid having a negative value for speed */
|
|
|
|
if (speed < 2)
|
|
|
|
speed = 0;
|
|
|
|
else
|
|
|
|
speed -= 2;
|
|
|
|
|
|
|
|
/* Avoid speed overflow */
|
|
|
|
if (speed > 15)
|
|
|
|
return 15;
|
|
|
|
|
|
|
|
return (u16)speed;
|
2009-07-14 12:38:18 +07:00
|
|
|
}
|
|
|
|
|
2009-07-04 18:03:48 +07:00
|
|
|
static void set_res(struct v4l2_subdev *sd)
|
|
|
|
{
|
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
|
|
|
unsigned vstart, hstart;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The mt9v011 doesn't have scaling. So, in order to select the desired
|
|
|
|
* resolution, we're cropping at the middle of the sensor.
|
|
|
|
* hblank and vblank should be adjusted, in order to warrant that
|
|
|
|
* we'll preserve the line timings for 30 fps, no matter what resolution
|
|
|
|
* is selected.
|
2009-07-04 18:15:11 +07:00
|
|
|
* NOTE: datasheet says that width (and height) should be filled with
|
|
|
|
* width-1. However, this doesn't work, since one pixel per line will
|
|
|
|
* be missing.
|
2009-07-04 18:03:48 +07:00
|
|
|
*/
|
|
|
|
|
2011-06-02 22:17:51 +07:00
|
|
|
hstart = 20 + (640 - core->width) / 2;
|
2009-07-04 18:03:48 +07:00
|
|
|
mt9v011_write(sd, R02_MT9V011_COLSTART, hstart);
|
|
|
|
mt9v011_write(sd, R04_MT9V011_WIDTH, core->width);
|
|
|
|
mt9v011_write(sd, R05_MT9V011_HBLANK, 771 - core->width);
|
|
|
|
|
2009-07-14 12:39:19 +07:00
|
|
|
vstart = 8 + (480 - core->height) / 2;
|
2009-07-04 18:03:48 +07:00
|
|
|
mt9v011_write(sd, R01_MT9V011_ROWSTART, vstart);
|
|
|
|
mt9v011_write(sd, R03_MT9V011_HEIGHT, core->height);
|
|
|
|
mt9v011_write(sd, R06_MT9V011_VBLANK, 508 - core->height);
|
2009-07-14 12:38:18 +07:00
|
|
|
|
2009-08-07 07:03:35 +07:00
|
|
|
calc_fps(sd, NULL, NULL);
|
2009-07-04 18:03:48 +07:00
|
|
|
};
|
|
|
|
|
2009-08-07 11:09:54 +07:00
|
|
|
static void set_read_mode(struct v4l2_subdev *sd)
|
|
|
|
{
|
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
|
|
|
unsigned mode = 0x1000;
|
|
|
|
|
|
|
|
if (core->hflip)
|
|
|
|
mode |= 0x4000;
|
|
|
|
|
|
|
|
if (core->vflip)
|
|
|
|
mode |= 0x8000;
|
|
|
|
|
|
|
|
mt9v011_write(sd, R20_MT9V011_READ_MODE, mode);
|
|
|
|
}
|
|
|
|
|
2009-06-29 15:41:26 +07:00
|
|
|
static int mt9v011_reset(struct v4l2_subdev *sd, u32 val)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE(mt9v011_init_default); i++)
|
|
|
|
mt9v011_write(sd, mt9v011_init_default[i].reg,
|
|
|
|
mt9v011_init_default[i].value);
|
|
|
|
|
|
|
|
set_balance(sd);
|
2009-07-04 18:03:48 +07:00
|
|
|
set_res(sd);
|
2009-08-07 11:09:54 +07:00
|
|
|
set_read_mode(sd);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
static int mt9v011_enum_mbus_fmt(struct v4l2_subdev *sd, unsigned index,
|
|
|
|
enum v4l2_mbus_pixelcode *code)
|
2009-07-04 18:03:48 +07:00
|
|
|
{
|
2010-05-09 20:19:25 +07:00
|
|
|
if (index > 0)
|
2009-07-04 18:03:48 +07:00
|
|
|
return -EINVAL;
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
*code = V4L2_MBUS_FMT_SGRBG8_1X8;
|
2009-07-04 18:03:48 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
static int mt9v011_try_mbus_fmt(struct v4l2_subdev *sd, struct v4l2_mbus_framefmt *fmt)
|
2009-07-04 18:03:48 +07:00
|
|
|
{
|
2010-05-09 20:19:25 +07:00
|
|
|
if (fmt->code != V4L2_MBUS_FMT_SGRBG8_1X8)
|
2009-07-04 18:03:48 +07:00
|
|
|
return -EINVAL;
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
v4l_bound_align_image(&fmt->width, 48, 639, 1,
|
|
|
|
&fmt->height, 32, 480, 1, 0);
|
|
|
|
fmt->field = V4L2_FIELD_NONE;
|
|
|
|
fmt->colorspace = V4L2_COLORSPACE_SRGB;
|
2009-07-04 18:03:48 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-08-07 07:03:35 +07:00
|
|
|
static int mt9v011_g_parm(struct v4l2_subdev *sd, struct v4l2_streamparm *parms)
|
|
|
|
{
|
|
|
|
struct v4l2_captureparm *cp = &parms->parm.capture;
|
|
|
|
|
|
|
|
if (parms->type != V4L2_BUF_TYPE_VIDEO_CAPTURE)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
memset(cp, 0, sizeof(struct v4l2_captureparm));
|
|
|
|
cp->capability = V4L2_CAP_TIMEPERFRAME;
|
|
|
|
calc_fps(sd,
|
|
|
|
&cp->timeperframe.numerator,
|
|
|
|
&cp->timeperframe.denominator);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mt9v011_s_parm(struct v4l2_subdev *sd, struct v4l2_streamparm *parms)
|
|
|
|
{
|
|
|
|
struct v4l2_captureparm *cp = &parms->parm.capture;
|
|
|
|
struct v4l2_fract *tpf = &cp->timeperframe;
|
|
|
|
u16 speed;
|
|
|
|
|
|
|
|
if (parms->type != V4L2_BUF_TYPE_VIDEO_CAPTURE)
|
|
|
|
return -EINVAL;
|
|
|
|
if (cp->extendedmode != 0)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
speed = calc_speed(sd, tpf->numerator, tpf->denominator);
|
|
|
|
|
|
|
|
mt9v011_write(sd, R0A_MT9V011_CLK_SPEED, speed);
|
|
|
|
v4l2_dbg(1, debug, sd, "Setting speed to %d\n", speed);
|
|
|
|
|
|
|
|
/* Recalculate and update fps info */
|
|
|
|
calc_fps(sd, &tpf->numerator, &tpf->denominator);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
static int mt9v011_s_mbus_fmt(struct v4l2_subdev *sd, struct v4l2_mbus_framefmt *fmt)
|
2009-07-04 18:03:48 +07:00
|
|
|
{
|
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
|
|
|
int rc;
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
rc = mt9v011_try_mbus_fmt(sd, fmt);
|
2009-07-04 18:03:48 +07:00
|
|
|
if (rc < 0)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2010-05-09 20:19:25 +07:00
|
|
|
core->width = fmt->width;
|
|
|
|
core->height = fmt->height;
|
2009-07-04 18:03:48 +07:00
|
|
|
|
|
|
|
set_res(sd);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-06-29 15:41:26 +07:00
|
|
|
#ifdef CONFIG_VIDEO_ADV_DEBUG
|
|
|
|
static int mt9v011_g_register(struct v4l2_subdev *sd,
|
|
|
|
struct v4l2_dbg_register *reg)
|
|
|
|
{
|
|
|
|
reg->val = mt9v011_read(sd, reg->reg & 0xff);
|
|
|
|
reg->size = 2;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mt9v011_s_register(struct v4l2_subdev *sd,
|
2013-03-24 18:28:46 +07:00
|
|
|
const struct v4l2_dbg_register *reg)
|
2009-06-29 15:41:26 +07:00
|
|
|
{
|
|
|
|
mt9v011_write(sd, reg->reg & 0xff, reg->val & 0xffff);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2012-09-07 15:42:15 +07:00
|
|
|
static int mt9v011_s_ctrl(struct v4l2_ctrl *ctrl)
|
|
|
|
{
|
|
|
|
struct mt9v011 *core =
|
|
|
|
container_of(ctrl->handler, struct mt9v011, ctrls);
|
|
|
|
struct v4l2_subdev *sd = &core->sd;
|
|
|
|
|
|
|
|
switch (ctrl->id) {
|
|
|
|
case V4L2_CID_GAIN:
|
|
|
|
core->global_gain = ctrl->val;
|
|
|
|
break;
|
|
|
|
case V4L2_CID_EXPOSURE:
|
|
|
|
core->exposure = ctrl->val;
|
|
|
|
break;
|
|
|
|
case V4L2_CID_RED_BALANCE:
|
|
|
|
core->red_bal = ctrl->val;
|
|
|
|
break;
|
|
|
|
case V4L2_CID_BLUE_BALANCE:
|
|
|
|
core->blue_bal = ctrl->val;
|
|
|
|
break;
|
|
|
|
case V4L2_CID_HFLIP:
|
|
|
|
core->hflip = ctrl->val;
|
|
|
|
set_read_mode(sd);
|
|
|
|
return 0;
|
|
|
|
case V4L2_CID_VFLIP:
|
|
|
|
core->vflip = ctrl->val;
|
|
|
|
set_read_mode(sd);
|
|
|
|
return 0;
|
|
|
|
default:
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
set_balance(sd);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct v4l2_ctrl_ops mt9v011_ctrl_ops = {
|
2009-06-29 15:41:26 +07:00
|
|
|
.s_ctrl = mt9v011_s_ctrl,
|
2012-09-07 15:42:15 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
static const struct v4l2_subdev_core_ops mt9v011_core_ops = {
|
2009-06-29 15:41:26 +07:00
|
|
|
.reset = mt9v011_reset,
|
|
|
|
#ifdef CONFIG_VIDEO_ADV_DEBUG
|
|
|
|
.g_register = mt9v011_g_register,
|
|
|
|
.s_register = mt9v011_s_register,
|
|
|
|
#endif
|
|
|
|
};
|
|
|
|
|
2009-07-04 18:03:48 +07:00
|
|
|
static const struct v4l2_subdev_video_ops mt9v011_video_ops = {
|
2010-05-09 20:19:25 +07:00
|
|
|
.enum_mbus_fmt = mt9v011_enum_mbus_fmt,
|
|
|
|
.try_mbus_fmt = mt9v011_try_mbus_fmt,
|
|
|
|
.s_mbus_fmt = mt9v011_s_mbus_fmt,
|
2009-08-07 07:03:35 +07:00
|
|
|
.g_parm = mt9v011_g_parm,
|
|
|
|
.s_parm = mt9v011_s_parm,
|
2009-07-04 18:03:48 +07:00
|
|
|
};
|
|
|
|
|
2009-06-29 15:41:26 +07:00
|
|
|
static const struct v4l2_subdev_ops mt9v011_ops = {
|
2009-07-04 18:03:48 +07:00
|
|
|
.core = &mt9v011_core_ops,
|
|
|
|
.video = &mt9v011_video_ops,
|
2009-06-29 15:41:26 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
/****************************************************************************
|
|
|
|
I2C Client & Driver
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
static int mt9v011_probe(struct i2c_client *c,
|
|
|
|
const struct i2c_device_id *id)
|
|
|
|
{
|
2009-07-04 18:03:48 +07:00
|
|
|
u16 version;
|
2009-06-29 15:41:26 +07:00
|
|
|
struct mt9v011 *core;
|
|
|
|
struct v4l2_subdev *sd;
|
|
|
|
|
|
|
|
/* Check if the adapter supports the needed features */
|
|
|
|
if (!i2c_check_functionality(c->adapter,
|
|
|
|
I2C_FUNC_SMBUS_READ_BYTE | I2C_FUNC_SMBUS_WRITE_BYTE_DATA))
|
|
|
|
return -EIO;
|
|
|
|
|
2013-05-02 18:29:43 +07:00
|
|
|
core = devm_kzalloc(&c->dev, sizeof(struct mt9v011), GFP_KERNEL);
|
2009-06-29 15:41:26 +07:00
|
|
|
if (!core)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
sd = &core->sd;
|
|
|
|
v4l2_i2c_subdev_init(sd, c, &mt9v011_ops);
|
2009-07-04 18:03:48 +07:00
|
|
|
|
|
|
|
/* Check if the sensor is really a MT9V011 */
|
|
|
|
version = mt9v011_read(sd, R00_MT9V011_CHIP_VERSION);
|
2009-07-27 18:24:29 +07:00
|
|
|
if ((version != MT9V011_VERSION) &&
|
|
|
|
(version != MT9V011_REV_B_VERSION)) {
|
|
|
|
v4l2_info(sd, "*** unknown micron chip detected (0x%04x).\n",
|
2009-07-04 18:03:48 +07:00
|
|
|
version);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2012-09-07 15:42:15 +07:00
|
|
|
v4l2_ctrl_handler_init(&core->ctrls, 5);
|
|
|
|
v4l2_ctrl_new_std(&core->ctrls, &mt9v011_ctrl_ops,
|
|
|
|
V4L2_CID_GAIN, 0, (1 << 12) - 1 - 0x20, 1, 0x20);
|
|
|
|
v4l2_ctrl_new_std(&core->ctrls, &mt9v011_ctrl_ops,
|
|
|
|
V4L2_CID_EXPOSURE, 0, 2047, 1, 0x01fc);
|
|
|
|
v4l2_ctrl_new_std(&core->ctrls, &mt9v011_ctrl_ops,
|
|
|
|
V4L2_CID_RED_BALANCE, -(1 << 9), (1 << 9) - 1, 1, 0);
|
|
|
|
v4l2_ctrl_new_std(&core->ctrls, &mt9v011_ctrl_ops,
|
|
|
|
V4L2_CID_BLUE_BALANCE, -(1 << 9), (1 << 9) - 1, 1, 0);
|
|
|
|
v4l2_ctrl_new_std(&core->ctrls, &mt9v011_ctrl_ops,
|
|
|
|
V4L2_CID_HFLIP, 0, 1, 1, 0);
|
|
|
|
v4l2_ctrl_new_std(&core->ctrls, &mt9v011_ctrl_ops,
|
|
|
|
V4L2_CID_VFLIP, 0, 1, 1, 0);
|
|
|
|
|
|
|
|
if (core->ctrls.error) {
|
|
|
|
int ret = core->ctrls.error;
|
|
|
|
|
|
|
|
v4l2_err(sd, "control initialization error %d\n", ret);
|
|
|
|
v4l2_ctrl_handler_free(&core->ctrls);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
core->sd.ctrl_handler = &core->ctrls;
|
|
|
|
|
2009-07-04 18:03:48 +07:00
|
|
|
core->global_gain = 0x0024;
|
2011-06-02 22:43:14 +07:00
|
|
|
core->exposure = 0x01fc;
|
2009-07-04 18:03:48 +07:00
|
|
|
core->width = 640;
|
|
|
|
core->height = 480;
|
2009-07-14 12:38:18 +07:00
|
|
|
core->xtal = 27000000; /* Hz */
|
2009-07-04 18:03:48 +07:00
|
|
|
|
2011-01-08 17:08:02 +07:00
|
|
|
if (c->dev.platform_data) {
|
|
|
|
struct mt9v011_platform_data *pdata = c->dev.platform_data;
|
|
|
|
|
|
|
|
core->xtal = pdata->xtal;
|
|
|
|
v4l2_dbg(1, debug, sd, "xtal set to %d.%03d MHz\n",
|
|
|
|
core->xtal / 1000000, (core->xtal / 1000) % 1000);
|
|
|
|
}
|
|
|
|
|
2009-07-27 18:24:29 +07:00
|
|
|
v4l_info(c, "chip found @ 0x%02x (%s - chip version 0x%04x)\n",
|
|
|
|
c->addr << 1, c->adapter->name, version);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mt9v011_remove(struct i2c_client *c)
|
|
|
|
{
|
|
|
|
struct v4l2_subdev *sd = i2c_get_clientdata(c);
|
2012-09-07 15:42:15 +07:00
|
|
|
struct mt9v011 *core = to_mt9v011(sd);
|
2009-06-29 15:41:26 +07:00
|
|
|
|
|
|
|
v4l2_dbg(1, debug, sd,
|
|
|
|
"mt9v011.c: removing mt9v011 adapter on address 0x%x\n",
|
|
|
|
c->addr << 1);
|
|
|
|
|
|
|
|
v4l2_device_unregister_subdev(sd);
|
2012-09-07 15:42:15 +07:00
|
|
|
v4l2_ctrl_handler_free(&core->ctrls);
|
2013-05-02 18:29:43 +07:00
|
|
|
|
2009-06-29 15:41:26 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------------- */
|
|
|
|
|
|
|
|
static const struct i2c_device_id mt9v011_id[] = {
|
|
|
|
{ "mt9v011", 0 },
|
|
|
|
{ }
|
|
|
|
};
|
|
|
|
MODULE_DEVICE_TABLE(i2c, mt9v011_id);
|
|
|
|
|
2010-09-16 01:09:38 +07:00
|
|
|
static struct i2c_driver mt9v011_driver = {
|
|
|
|
.driver = {
|
|
|
|
.owner = THIS_MODULE,
|
|
|
|
.name = "mt9v011",
|
|
|
|
},
|
|
|
|
.probe = mt9v011_probe,
|
|
|
|
.remove = mt9v011_remove,
|
|
|
|
.id_table = mt9v011_id,
|
2009-06-29 15:41:26 +07:00
|
|
|
};
|
2010-09-16 01:09:38 +07:00
|
|
|
|
2012-02-12 16:56:32 +07:00
|
|
|
module_i2c_driver(mt9v011_driver);
|