All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Herbrechtsmeier <hbmeier@hni.uni-paderborn.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: OmniVision OV9655 camera chip via soc-camera interface
Date: Tue, 15 Apr 2008 11:39:09 +0200	[thread overview]
Message-ID: <480477BD.5090900@hni.uni-paderborn.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0804142224570.5332@axis700.grange>

Guennadi Liakhovetski schrieb:
> On Mon, 14 Apr 2008, Stefan Herbrechtsmeier wrote:
>
>   
>> I'm writing a driver for the OmniVision OV9655 camera chip connected to a
>> PXA270 processor. I based my work on the soc_camera interface, but I need some
>> additional gpios for reset and power_enable. What is the best way to pass this
>> information to the driver?
>>     
>
> Look in pxa_camera.c, e.g., in pxa_camera_activate. There are function calls like
>
> pxa_camera_activate(struct pxa_camera_dev *pcdev)
> {
> 	struct pxacamera_platform_data *pdata = pcdev->pdata;
>
> ...
>
> 	pdata->power(pcdev->dev, 1);
>
> ...
>
> 	pdata->reset(pcdev->dev, 1);
>
> in it, which should do exactly what you need. And they are supposed to be 
> implemented in the platform, so, you have all the required GPIO 
> information you need there. That is exactly the reason they are defined 
> that way - because they were thought to be platform-dependent. Let me know 
> if there's still anything missing. It is still a work in progress, so, we 
> are flexible and can add any (reasonable) APIs we find useful.
>   
Thanks, that exact what I search, but maybe this functions should be in 
the soc_camera_link. I think this functions belong to the camera chip 
and not to the capture interface. This allows more than one camera chip 
on one capture interface with separate enable and reset.
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski
>   
Thanks
    Stefan

-- 
Dipl.-Ing. Stefan Herbrechtsmeier

Heinz Nixdorf Institute
University of Paderborn 
System and Circuit Technology 
Fürstenallee 11
D-33102 Paderborn (Germany)

office : F0.415
phone  : + 49 5251 - 60 6342
fax    : + 49 5251 - 60 6351

mailto : hbmeier@hni.upb.de

www    : http://wwwhni.upb.de/sct/mitarbeiter/hbmeier


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-04-15  9:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  8:01 OmniVision OV9655 camera chip via soc-camera interface Stefan Herbrechtsmeier
2008-04-14 11:20 ` Jaime Velasco
2008-04-15  9:17   ` Stefan Herbrechtsmeier
2008-04-14 20:30 ` Guennadi Liakhovetski
2008-04-15  9:39   ` Stefan Herbrechtsmeier [this message]
2008-04-15 10:45     ` Guennadi Liakhovetski
2008-05-02  9:30       ` Stefan Herbrechtsmeier
     [not found]       ` <481ADED1.8050201@hni.uni-paderborn.de>
2008-05-02  9:49         ` Guennadi Liakhovetski
2008-05-02 11:11           ` Stefan Herbrechtsmeier
2008-05-02 11:16             ` Guennadi Liakhovetski
2008-05-02 11:29               ` Stefan Herbrechtsmeier
2008-05-02 16:11                 ` [PATCH] Some suggestions for the soc_camera interface Stefan Herbrechtsmeier
2008-05-02 19:53                   ` Guennadi Liakhovetski
2008-05-05 13:30                     ` Stefan Herbrechtsmeier
2008-05-05 15:27                       ` Guennadi Liakhovetski
2008-07-29 17:14                       ` Guennadi Liakhovetski
2008-07-30  8:02                         ` Stefan Herbrechtsmeier
2008-07-30  8:11                           ` Guennadi Liakhovetski
2008-07-30  8:57                             ` Paulius Zaleckas
2008-07-30  9:33                               ` Stefan Herbrechtsmeier
2008-07-30 10:33                                 ` Guennadi Liakhovetski

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=480477BD.5090900@hni.uni-paderborn.de \
    --to=hbmeier@hni.uni-paderborn.de \
    --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 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.