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] Move .power and .reset from soc_camera platform to sensor driver
Date: Fri, 01 Aug 2008 10:15:37 +0200	[thread overview]
Message-ID: <4892C629.5000208@hni.uni-paderborn.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0808010940400.14927@axis700.grange>

Guennadi Liakhovetski schrieb:
> On Fri, 1 Aug 2008, Stefan Herbrechtsmeier wrote:
>
>   
>> Guennadi Liakhovetski schrieb:
>>     
>>> As for calling either platform-provided reset or internal one. Actually,
>>> whyt about making platform reset (and power too) return an error code, and
>>> if it failed call th internal one? 
>>>       
>> At the moment I assume that reset and power will work, if they are defined,
>> but we can change it.
>>     
>
> 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.
>   
>>> And as a parameter wouldn't it make more sense to pass the soc_camera_link
>>> to the platform functions instead of the struct device from the i2c device?
>>>   
>>>       
>> I have simple make the function similar to other platform_data functions on my
>> system.
>> At the moment I use the parameter only for printing messages via dev_err.
>>     
>
> You have to be able to trace which camera has to be resetted / powered on 
> or off in your platform code, and the camera_link structure is the object 
> that identifies a specific camera, ot, at least, it can be. Whereas the 
> device pointer doesn't easily tell you which camera you want to operate 
> upon.
>   
If you use the same function for different sensors (camera_links), you 
are right,
but you can get the camera_link from the dev pointer (.platform_data) if you
need it.

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-01  8:15 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 [this message]
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
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=4892C629.5000208@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.