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,
	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 06:57:28 +0200	[thread overview]
Message-ID: <48A3BB38.7010301@hni.uni-paderborn.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0808131456140.5389@axis700.grange>

Guennadi Liakhovetski schrieb:
> Make .power and .reset callbacks per camera instead of per host, also move 
> their invocation to camera drivers.
>
> Signed-off-by: Stefan Herbrechtsmeier <hbmeier@hni.uni-paderborn.de>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>
> On Fri, 1 Aug 2008, Stefan Herbrechtsmeier wrote:
>   
>> Guennadi Liakhovetski schrieb:
>>     
>>> I'd rather preserve the possibility to use "soft" reset / poweroff also when
>>> a platform function is defined. In fact, it might be even better to do a
>>> soft power-off first and then call platform-provided one. Don't think it
>>> would make much sense for reset though.
>>>   
>>>       
>> You are right, I'll change it with the next version.
>>     
>
> 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.

The patch looks ok for me.

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

  reply	other threads:[~2008-08-14  4:57 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 [this message]
2008-08-14  5:12                 ` Guennadi Liakhovetski
2008-08-14  6:13                   ` Stefan Herbrechtsmeier
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=48A3BB38.7010301@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.