linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Sedji Gaouaou <sedji.gaouaou@atmel.com>
Cc: Andy Walls <awalls@md.metrocast.net>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: question about v4l2_subdev
Date: Tue, 01 Jun 2010 16:04:13 +0200	[thread overview]
Message-ID: <4C05135D.1080108@atmel.com> (raw)
In-Reply-To: <4C04C17D.8020702@atmel.com>

Hi,

Sorry to bother you again, but here is the situation:
I have 2 drivers: an ov2640 driver and my atmel driver.
Basically the ov2640 driver is the same as the ov7670 driver.

So what I don't know is how to call the ov2640 functions(such as set 
format) in my atmel driver.

In the ov2640 I used the function: v4l2_i2c_subdev_init, and in the 
atmel driver I used v4l2_device_register.

But I don't know where I should use the v4l2_i2c_new_subdev function, 
and how to link my atmel video struct to the i2c sensor.

Is there any examples in linux?

Regards,
Sedji

Le 6/1/2010 10:14 AM, Sedji Gaouaou a écrit :
> Hi,
>
>
>>
>> 1. Something first should call v4l2_device_register() on a v4l2_device
>> object. (Typically there is only one v4l2_device object per "bridge"
>> chip between the PCI, PCIe, or USB bus and the subdevices, even if that
>> bridge chip has more than one I2C master implementation.)
>>
>> 2. Then, for subdevices connected to the bridge chip via I2C, something
>> needs to call v4l2_i2c_new_subdev() with the v4l2_device pointer as one
>> of the arguments, to get back a v4l2_subdevice instance pointer.
>>
>> 3. After that, v4l2_subdev_call() with the v4l2_subdev pointer as one of
>> the arguments can be used to invoke the subdevice methods.
>>
>> TV Video capture drivers do this work themselves. Drivers using a
>> camera framework may have the framework doing some of the work for them.
>>
>>
>> Regards,
>> Andy
>>
>>
>>
>
>
> Is there a sensor driver which is using this method?
>
> To write the ov2640 driver I have just copied the ov7670.c file, and I
> didn't find the v4l2_i2c_new_subdev in it...
>
> Regards,
> Sedji
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2010-06-01 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 15:38 question about v4l2_subdev Sedji Gaouaou
2010-05-31 18:19 ` Andy Walls
2010-06-01  8:14   ` Sedji Gaouaou
2010-06-01 14:04     ` Sedji Gaouaou [this message]
2010-06-01 20:56       ` David Ellingsworth
2010-06-05  1:27     ` Andy Walls
2010-06-07 10:01       ` Sedji Gaouaou

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=4C05135D.1080108@atmel.com \
    --to=sedji.gaouaou@atmel.com \
    --cc=awalls@md.metrocast.net \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-input@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).