From: Stefan Herbrechtsmeier <hbmeier@hni.uni-paderborn.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com,
Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
Subject: Re: [PATCH] soc-camera: Move .power and .reset from soc_camera host to sensor driver
Date: Thu, 14 Aug 2008 08:13:35 +0200 [thread overview]
Message-ID: <48A3CD0F.9050509@hni.uni-paderborn.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0808140705550.12600@axis700.grange>
Guennadi Liakhovetski schrieb:
> On Thu, 14 Aug 2008, Stefan Herbrechtsmeier wrote:
>
>
>> Guennadi Liakhovetski schrieb:
>>
>>> How about the version below? I didn't understand why you need extra .init
>>> and .release calls, so, I removed them for now. I think, .init per host and
>>> power-on / off per camera should be enough for all init / release needs,
>>> don't you think so
>>>
>> I use the .init call for gpio_request and gpio_direction_output and the
>> .release call for gpio_free.
>> I do that this way, because I think they belongs more to the camera.
>>
>
> What are these GPIOs? Are they interfacing to a specific camera, or do
> they belong to the camera-host interface? If they belong to a specific
> camera, then yes, it is logical to control them from the camera driver
> platform callbacks.
The GPIOs belongs to the camera. One GPIO for the camera reset input and
one for the power down
input of the camera.
> But cannot you do this in .power? Just do the .init
> part on power-on and the .release part on power-off?
>
The driver need to control the power down input after power-off to hold
the camera in power down mode.
Maybe I can free the gpio after power-off without changing the gpio
value, but I think the use of .init and
.release call is better and more clearly. Do you think it is ok to free
the gpio even if it must stay high?
>
>> The patch looks ok for me.
>>
>
> Well, if you cannot use it in this form without .init and .release then it
> can hardly be called "ok" for you:-)
>
I mean it is ok except the .init and .release part. ;-)
Regards
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
next prev parent reply other threads:[~2008-08-14 6:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 6:02 [PATCH] Move .power and .reset from soc_camera platform to sensor driver Stefan Herbrechtsmeier
2008-07-31 13:53 ` Paulius Zaleckas
[not found] ` <48917CB5.6000304@teltonika.lt>
2008-08-01 6:11 ` Stefan Herbrechtsmeier
2008-08-01 6:25 ` Guennadi Liakhovetski
2008-08-01 7:35 ` Stefan Herbrechtsmeier
2008-08-01 7:45 ` Guennadi Liakhovetski
2008-08-01 8:15 ` Stefan Herbrechtsmeier
2008-08-13 13:30 ` [PATCH] soc-camera: Move .power and .reset from soc_camera host " Guennadi Liakhovetski
2008-08-14 4:57 ` Stefan Herbrechtsmeier
2008-08-14 5:12 ` Guennadi Liakhovetski
2008-08-14 6:13 ` Stefan Herbrechtsmeier [this message]
2008-08-14 6:24 ` Guennadi Liakhovetski
2008-08-14 6:37 ` Stefan Herbrechtsmeier
2008-08-01 8:24 ` [PATCH] Move .power and .reset from soc_camera platform " Paulius Zaleckas
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=48A3CD0F.9050509@hni.uni-paderborn.de \
--to=hbmeier@hni.uni-paderborn.de \
--cc=g.liakhovetski@gmx.de \
--cc=paulius.zaleckas@teltonika.lt \
--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.