Driver fails to initialize due to insane settings in the
control init array.

Fix this by moving to sanity.

Signed-off-by: Andy Shevchenko <andriy.shevche...@linux.intel.com>
---
 drivers/staging/media/atomisp/i2c/atomisp-lm3554.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/staging/media/atomisp/i2c/atomisp-lm3554.c 
b/drivers/staging/media/atomisp/i2c/atomisp-lm3554.c
index 4fd9f538ac95..974b6ff50c7a 100644
--- a/drivers/staging/media/atomisp/i2c/atomisp-lm3554.c
+++ b/drivers/staging/media/atomisp/i2c/atomisp-lm3554.c
@@ -562,10 +562,10 @@ static const struct v4l2_ctrl_config lm3554_controls[] = {
        {
         .ops = &ctrl_ops,
         .id = V4L2_CID_FLASH_STATUS,
-        .type = V4L2_CTRL_TYPE_BOOLEAN,
+        .type = V4L2_CTRL_TYPE_INTEGER,
         .name = "Flash Status",
-        .min = 0,
-        .max = 100,
+        .min = ATOMISP_FLASH_STATUS_OK,
+        .max = ATOMISP_FLASH_STATUS_TIMEOUT,
         .step = 1,
         .def = ATOMISP_FLASH_STATUS_OK,
         .flags = 0,
@@ -574,10 +574,10 @@ static const struct v4l2_ctrl_config lm3554_controls[] = {
        {
         .ops = &ctrl_ops,
         .id = V4L2_CID_FLASH_STATUS_REGISTER,
-        .type = V4L2_CTRL_TYPE_BOOLEAN,
+        .type = V4L2_CTRL_TYPE_INTEGER,
         .name = "Flash Status Register",
         .min = 0,
-        .max = 100,
+        .max = 255,
         .step = 1,
         .def = 0,
         .flags = 0,
-- 
2.15.1

Reply via email to