public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Subject: Re: [PATCH] V4L: fix ov9650 control clusters
Date: Sun, 24 Jan 2016 23:14:40 +0200	[thread overview]
Message-ID: <161527698.XeG1cnYavA@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1601191211300.15265@axis700.grange>

Hi Guennadi,

Thank you for the patch.

On Tuesday 19 January 2016 12:12:48 Guennadi Liakhovetski wrote:
> Auto-gain and auto-exposure clusters in the ov9650 driver have both a
> size of 2, not 3 controls. Fix this.
> 
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>

Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

I'd change the subject to "v4l: ov9650: Fix control clusters" though.

> ---
>  drivers/media/i2c/ov9650.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/media/i2c/ov9650.c b/drivers/media/i2c/ov9650.c
> index 9fe9006..2baa528 100644
> --- a/drivers/media/i2c/ov9650.c
> +++ b/drivers/media/i2c/ov9650.c
> @@ -1046,8 +1046,8 @@ static int ov965x_initialize_controls(struct ov965x
> *ov965x) ctrls->exposure->flags |= V4L2_CTRL_FLAG_VOLATILE;
> 
>  	v4l2_ctrl_auto_cluster(3, &ctrls->auto_wb, 0, false);
> -	v4l2_ctrl_auto_cluster(3, &ctrls->auto_gain, 0, true);
> -	v4l2_ctrl_auto_cluster(3, &ctrls->auto_exp, 1, true);
> +	v4l2_ctrl_auto_cluster(2, &ctrls->auto_gain, 0, true);
> +	v4l2_ctrl_auto_cluster(2, &ctrls->auto_exp, 1, true);
>  	v4l2_ctrl_cluster(2, &ctrls->hflip);
> 
>  	ov965x->sd.ctrl_handler = hdl;

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2016-01-25  6:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 11:12 [PATCH] V4L: fix ov9650 control clusters Guennadi Liakhovetski
2016-01-24 21:14 ` Laurent Pinchart [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=161527698.XeG1cnYavA@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=sylvester.nawrocki@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox