From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Javier Martin" <javier.martin@vista-silicon.com>,
"Gaëtan Carlier" <gcembed@gmail.com>,
"Mauro Carvalho Chehab" <mchehab@redhat.com>,
"Guennadi Liakhovetski" <g.liakhovetski@gmx.de>,
"Sascha Hauer" <kernel@pengutronix.de>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: Camera not detected on linux-next
Date: Wed, 05 Sep 2012 18:17:36 +0200 [thread overview]
Message-ID: <50477B20.1030902@samsung.com> (raw)
In-Reply-To: <CAOMZO5D7Ar0SE9vmi41jSxbPqv8sSOQshbL6Uzv4Ltow5xKx4w@mail.gmail.com>
Hi,
On 09/05/2012 06:06 PM, Fabio Estevam wrote:
> I am running linux-next 20120905 on a mx31pdk board with a ov2640 CMOS
> and I am not able to get the ov2640 to be probed:
>
> soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
> mx3-camera mx3-camera.0: MX3 Camera driver attached to camera 0
> mx3-camera mx3-camera.0: MX3 Camera driver detached from camera 0
> .... (no messages showing ov2640 being probed)
>
> I noticed that Kconfig changed the way to select the "Sensors used on
> soc_camera driver" and I selected ov2640 in the .config.
>
> camera worked fine on this board running 3.5.3. So before start
> bisecting, I would like to know if there is anything obvious I am
> missing.
>
> Also tested on a mx27pdk and ov2640 could not be probed there as well.
Maybe this is about the sensor/host driver linking order.
If so, then this patch should help
http://git.linuxtv.org/snawrocki/media.git/commitdiff/458b9b5ab8cb970887c9d1f1fddf88399b2d9ef2
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-09-05 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 16:06 Camera not detected on linux-next Fabio Estevam
2012-09-05 16:17 ` Sylwester Nawrocki [this message]
2012-09-05 16:28 ` Fabio Estevam
2012-09-06 9:16 ` Prabhakar Lad
2012-09-06 10:49 ` Sylwester Nawrocki
2012-09-06 11:08 ` Prabhakar Lad
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=50477B20.1030902@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=festevam@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=gcembed@gmail.com \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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