diff options
| author | Jacopo Mondi <[email protected]> | 2017-05-12 09:36:59 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2017-06-23 08:28:05 -0300 |
| commit | ab924af9acde26a5840b905c599dd4f3e10eaa00 (patch) | |
| tree | 8a3746134d92e53f9c7a75e7af9bcd415fb1d339 /drivers/media/platform/vimc/vimc-sensor.c | |
| parent | affd250dec1717e225fa2015ad6b238a43d5aca5 (diff) | |
[media] media: i2c: ov772x: Force use of SCCB protocol
Commit e78902976150 ("i2c: sh_mobile: don't send a stop condition by
default inside transfers") makes the i2c_sh_mobile I2C-adapter emit a
stop/start sequence between messages in a single transfer only when
explicitly requested with I2C_M_STOP.
This breaks the ov772x driver in the SH4 Migo-R board as the Omnivision
sensor uses the I2C-like SCCB protocol that doesn't support repeated
starts:
i2c-sh_mobile i2c-sh_mobile.0: Transfer request timed out
ov772x 0-0021: Product ID error 92:92
Fix it by marking the client as SCCB, forcing the emission of a
stop/start sequence between all messages.
As I2C_M_STOP requires the I2C adapter to support protocol mangling,
ensure that the I2C_FUNC_PROTOCOL_MANGLING functionality is available.
Tested on SH4 Migo-R board, with OV772x now successfully probing
soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
ov772x 0-0021: ov7725 Product ID 77:21 Manufacturer ID 7f:a2
Signed-off-by: Jacopo Mondi <[email protected]>
Suggested-by: Laurent Pinchart <[email protected]>
Acked-by: Wolfram Sang <[email protected]>
Reviewed-by: Laurent Pinchart <[email protected]>
Signed-off-by: Sakari Ailus <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'drivers/media/platform/vimc/vimc-sensor.c')
0 files changed, 0 insertions, 0 deletions