All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 1/4] soc-camera: add board hook to specify the buswidth for camera sensors
Date: Thu, 12 Mar 2009 09:11:26 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0903120856210.4896@axis700.grange> (raw)
In-Reply-To: <1236765976-20581-2-git-send-email-s.hauer@pengutronix.de>

On Wed, 11 Mar 2009, Sascha Hauer wrote:

> Camera sensors have a native bus width say support, but on some
> boards not all sensor data lines are connected to the image
> interface and thus support a different bus width than the sensors
> native one. Some boards even have a bus driver which dynamically
> switches between different bus widths with a GPIO.
> 
> This patch adds a hook which board code can use to support different
> bus widths.
> 
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  include/media/soc_camera.h |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/include/media/soc_camera.h b/include/media/soc_camera.h
> index 7440d92..d68959c 100644
> --- a/include/media/soc_camera.h
> +++ b/include/media/soc_camera.h
> @@ -100,6 +100,12 @@ struct soc_camera_link {
>  	/* Optional callbacks to power on or off and reset the sensor */
>  	int (*power)(struct device *, int);
>  	int (*reset)(struct device *);
> +	/* some platforms may support different data widths than the sensors
> +	 * native ones due to different data line routing. Let the board code
> +	 * overwrite the width flags.
> +	 */

Please, format the comment according to CodingStyle:

	/*
	 * some
	 * comment
	 */

I know, I have some non-conforming (similar to yours) comments in 
soc-camera .c files, but this header is "clean" so far:-) Let's keep it 
that way.

> +	int (*set_bus_param)(struct device *, unsigned long flags);
> +	unsigned long (*query_bus_param)(struct device *);

Wouldn't the first parameter of type "struct soc_camera_link *" make more 
sense? I'll also then change .power and .reset similarly.

>  };
>  
>  static inline struct soc_camera_device *to_soc_camera_dev(struct device *dev)
> -- 
> 1.5.6.5
> 

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

      parent reply	other threads:[~2009-03-12  8:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 10:06 [PATCH 0/4] soc-camera: setting the buswidth of camera sensors Sascha Hauer
2009-03-11 10:06 ` [PATCH 1/4] soc-camera: add board hook to specify the buswidth for " Sascha Hauer
2009-03-11 10:06   ` [PATCH 2/4] pcm990 baseboard: add camera bus width switch setting Sascha Hauer
2009-03-11 10:06     ` [PATCH 3/4] mt9m001: allow setting of bus width from board code Sascha Hauer
2009-03-11 10:06       ` [PATCH 4/4] mt9v022: " Sascha Hauer
2009-03-12  9:43         ` Guennadi Liakhovetski
2009-03-12  9:21       ` [PATCH 3/4] mt9m001: " Guennadi Liakhovetski
2009-03-12  8:31     ` [PATCH 2/4] pcm990 baseboard: add camera bus width switch setting Guennadi Liakhovetski
2009-03-12  8:40       ` Sascha Hauer
2009-03-12  8:40     ` Guennadi Liakhovetski
2009-03-12  9:12       ` Sascha Hauer
2009-03-12  9:25         ` Guennadi Liakhovetski
2009-03-12  9:47           ` Sascha Hauer
2009-03-12  8:11   ` Guennadi Liakhovetski [this message]

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=Pine.LNX.4.64.0903120856210.4896@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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.