From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: atmel v4l2 soc driver
Date: Mon, 23 Mar 2009 16:21:03 +0100 [thread overview]
Message-ID: <49C7A8DF.3040101@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0903111100050.4818@axis700.grange>
Hi,
I am writing a driver for the ov9655 sensor from Omnivision.
To do so I am using the ov772x.c file as an example.
But I don't understant, because it seems that I never enter the
video_probe function...
Do you have any idea what could I do wrong? Is it coming from a wrong
i2c config?
Regards,
Sedji
Guennadi Liakhovetski a écrit :
> On Wed, 11 Mar 2009, Sedji Gaouaou wrote:
>
>> I am currently porting an atmel isi driver to the soc layer,
>
> This is good!
>
>> and I encounter some problems.
>> I have based my driver on pax-camera. and sh_mobile_ceu_camera.c.
>> The point is I can't see any video entry in /dev when I do ls dev/ on my
>> board...
>> So I wonder when is soc_camera_video_start(which call video_register_device)
>> called? Is that at the probe?
>
> Well, you could just do
>
> grep soc_camera_video_start drivers/media/video/*.c
>
> Then you would immediately see, that each specific camera (sensor,
> decoder, whatever) driver explicitly calls this function.
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
>
next prev parent reply other threads:[~2009-03-23 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 9:52 atmel v4l2 soc driver Sedji Gaouaou
2009-03-11 10:02 ` Guennadi Liakhovetski
2009-03-23 15:21 ` Sedji Gaouaou [this message]
2009-03-23 15:40 ` Guennadi Liakhovetski
2009-03-23 16:00 ` Sedji Gaouaou
2009-03-23 16:06 ` Guennadi Liakhovetski
2009-03-23 16:14 ` Sedji Gaouaou
2009-03-23 16:30 ` Guennadi Liakhovetski
2009-08-03 7:13 ` Guennadi Liakhovetski
[not found] ` <4AFC15E6.2000101@atmel.com>
2009-11-12 14:12 ` Guennadi Liakhovetski
2009-03-23 18:23 ` Hans Verkuil
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=49C7A8DF.3040101@atmel.com \
--to=sedji.gaouaou@atmel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.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.