From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ed1-f68.google.com ([209.85.208.68]:35712 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728414AbeJETsX (ORCPT ); Fri, 5 Oct 2018 15:48:23 -0400 From: Ricardo Ribalda Delgado To: Hans Verkuil , Laurent Pinchart , Sakari Ailus , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, jacopo@jmondi.org Cc: Ricardo Ribalda Delgado Subject: [PATCH v8 3/3] [media] imx214: Fix range for V4L2_CID_EXPOSURE Date: Fri, 5 Oct 2018 14:49:39 +0200 Message-Id: <20181005124940.15539-3-ricardo.ribalda@gmail.com> In-Reply-To: <20181005124940.15539-1-ricardo.ribalda@gmail.com> References: <20181005124940.15539-1-ricardo.ribalda@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-media-owner@vger.kernel.org List-ID: Going above 3184 changes the frame-rate of the sensor. Without this patch there is no way to change the exposure without affecting the frame-rate. With the proper documentation we should be able the change the frame-rate at wish, but until that happens we just cap what the sensor can do. Signed-off-by: Ricardo Ribalda Delgado --- drivers/media/i2c/imx214.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/i2c/imx214.c b/drivers/media/i2c/imx214.c index 46a2fdfbd049..0b99123161b8 100644 --- a/drivers/media/i2c/imx214.c +++ b/drivers/media/i2c/imx214.c @@ -1027,7 +1027,7 @@ static int imx214_probe(struct i2c_client *client) */ imx214->exposure = v4l2_ctrl_new_std(&imx214->ctrls, &imx214_ctrl_ops, V4L2_CID_EXPOSURE, - 0, 0xffff, 1, 0x0c70); + 0, 3184, 1, 0x0c70); ret = imx214->ctrls.error; if (ret) { -- 2.19.0