1 From 38aa34eae8e6aa8504f97f86ac155a0ebc6a0557 Mon Sep 17 00:00:00 2001
2 From: David Plowman <david.plowman@raspberrypi.org>
3 Date: Wed, 15 Jan 2020 13:40:38 +0000
4 Subject: [PATCH] media: ov5647: Fix return codes from
5 ov5647_write/ov5647_read functions.
7 Previously they were returning positive non-zero codes for success,
8 which were getting passed up the call stack. Since release 4.19,
9 do_dentry_open (fs/open.c) has been catching these and flagging an
10 error. (So this driver has been broken since that date.)
12 Fixes: 3c2472a [media] media: i2c: Add support for OV5647 sensor
13 Signed-off-by: David Plowman <david.plowman@raspberrypi.org>
14 Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
16 drivers/media/i2c/ov5647.c | 38 ++++++++++++++++++++++++++++++++------
17 1 file changed, 32 insertions(+), 6 deletions(-)
19 --- a/drivers/media/i2c/ov5647.c
20 +++ b/drivers/media/i2c/ov5647.c
21 @@ -587,7 +587,13 @@ static int ov5647_write16(struct v4l2_su
24 ret = i2c_master_send(client, data, 4);
27 + * Writing the wrong number of bytes also needs to be flagged as an
28 + * error. Success needs to produce a 0 return code.
33 dev_dbg(&client->dev, "%s: i2c write error, reg: %x\n",
36 @@ -603,10 +609,17 @@ static int ov5647_write(struct v4l2_subd
39 ret = i2c_master_send(client, data, 3);
42 + * Writing the wrong number of bytes also needs to be flagged as an
43 + * error. Success needs to produce a 0 return code.
48 dev_dbg(&client->dev, "%s: i2c write error, reg: %x\n",
56 @@ -619,17 +632,30 @@ static int ov5647_read(struct v4l2_subde
59 ret = i2c_master_send(client, data_w, 2);
62 + * A negative return code, or sending the wrong number of bytes, both
63 + * count as an error.
66 dev_dbg(&client->dev, "%s: i2c write error, reg: %x\n",
73 ret = i2c_master_recv(client, val, 1);
76 + * The only return value indicating success is 1. Anything else, even
77 + * a non-negative value, indicates something went wrong.
82 dev_dbg(&client->dev, "%s: i2c read error, reg: %x\n",