From: Mike Rapoport <mike@compulab.co.il>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: [PATCH] mt9m111: add support for mt9m112 since sensors seem identical
Date: Wed, 26 Nov 2008 11:43:09 +0200 [thread overview]
Message-ID: <492D1A2D.8070701@compulab.co.il> (raw)
In-Reply-To: <Pine.LNX.4.64.0811252225200.10677@axis700.grange>
Guennadi Liakhovetski wrote:
> On Tue, 25 Nov 2008, Mike Rapoport wrote:
>
>> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
>> ---
>> drivers/media/video/mt9m111.c | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/media/video/mt9m111.c b/drivers/media/video/mt9m111.c
>> index da0b2d5..49c1167 100644
>> --- a/drivers/media/video/mt9m111.c
>> +++ b/drivers/media/video/mt9m111.c
>> @@ -841,7 +841,8 @@ static int mt9m111_video_probe(struct soc_camera_device *icd)
>> data = reg_read(CHIP_VERSION);
>>
>> switch (data) {
>> - case 0x143a:
>> + case 0x143a: /* MT9M111 */
>> + case 0x148c: /* MT9M112 */
>> mt9m111->model = V4L2_IDENT_MT9M111;
>
> Wouldn't it be better to add a new chip ID? Are there any differences
> between the two models, that the user might want to know about?
I don't have mt9m111 datasheet, I can only judge by "feature comparison" table
in the mt9m112 datasheet. It seems that sensors differ in there advanced image
processing and low power mode capabilities.
If you think it's worse adding new chip ID, I'll prepare the patches.
> Thanks
> Guennadi
>
>> icd->formats = mt9m111_colour_formats;
>> icd->num_formats = ARRAY_SIZE(mt9m111_colour_formats);
>> --
>> 1.5.6.4
>>
>> --
>> video4linux-list mailing list
>> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/video4linux-list
>>
>
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
>
--
Sincerely yours,
Mike.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-11-26 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 8:59 [PATCH] mt9m111: add support for mt9m112 since sensors seem identical Mike Rapoport
2008-11-25 18:46 ` Robert Jarzmik
2008-11-25 21:30 ` Guennadi Liakhovetski
2008-11-26 9:43 ` Mike Rapoport [this message]
2008-11-30 7:38 ` Mike Rapoport
2008-12-01 8:30 ` Guennadi Liakhovetski
2008-12-03 8:01 ` [PATCH 1/2] " Mike Rapoport
2008-12-03 8:02 ` [PATCH 2/2] " Mike Rapoport
2008-12-03 8:14 ` Guennadi Liakhovetski
2008-12-03 8:23 ` Mike Rapoport
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=492D1A2D.8070701@compulab.co.il \
--to=mike@compulab.co.il \
--cc=g.liakhovetski@gmx.de \
--cc=video4linux-list@redhat.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