From: gcembed@gmail.com (Gaëtan Carlier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM : i.MX27 : split code for allocation of ressources of camera and eMMA
Date: Wed, 05 Sep 2012 17:50:15 +0200 [thread overview]
Message-ID: <504774B7.8090007@gmail.com> (raw)
In-Reply-To: <CAOMZO5DyjdrZYNDMuT1=yuxQcHuP3=6dy_j_ja1vub56_m3pvA@mail.gmail.com>
On 09/05/2012 05:29 PM, Fabio Estevam wrote:
> On Wed, Sep 5, 2012 at 12:03 PM, Ga?tan Carlier <gcembed@gmail.com> wrote:
>
>> With or without my patch ? I have burnt out my ov2640 while previous
>
> Without your patch. Just running a clean linux-next-20120905.
I also notice a difference between previous release. Before, if CMOS was
not scanned on I2C, soc-camera failed to init.
With this release, soc-camera driver loads and create dev node even when
nothing is connected on I2C bus.
>
>> experimentation so it is hard for me to test that and I have to write driver
>> for MT9V111 to be able to test soc-camera on Kernel 3.x.
>
> Write a driver? There is already one: drivers/media/i2c/mt9v011.c
MT9V011 is not compatible with MT9V111. MT9V111 uses two address spaces
for register : Sensor Core registers and IFP registers. Another MT9*
driver works with two address spaces but this is for a HD sensor and the
function of registers is different.
>
> Regards,
>
> Fabio Estevam
>
Regards,
Ga?tan Carlier.
next prev parent reply other threads:[~2012-09-05 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 12:56 [PATCH] ARM : i.MX27 : split code for allocation of ressources of camera and eMMA Gaëtan Carlier
2012-09-05 6:49 ` javier Martin
2012-09-05 7:37 ` Gaëtan Carlier
2012-09-05 8:22 ` javier Martin
2012-09-05 8:47 ` Gaëtan Carlier
2012-09-05 9:11 ` javier Martin
2012-09-05 9:35 ` Gaëtan Carlier
2012-09-05 9:51 ` javier Martin
2012-09-05 13:47 ` Fabio Estevam
2012-09-05 15:03 ` Gaëtan Carlier
2012-09-05 15:29 ` Fabio Estevam
2012-09-05 15:50 ` Gaëtan Carlier [this message]
2012-09-05 18:20 ` Fabio Estevam
2012-09-05 18:51 ` Gaëtan Carlier
2012-09-05 19:07 ` Fabio Estevam
2012-10-04 14:07 ` Fabio Estevam
2012-10-05 6:51 ` javier Martin
2012-10-05 21:55 ` Fabio Estevam
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=504774B7.8090007@gmail.com \
--to=gcembed@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.