summaryrefslogtreecommitdiff
path: root/drivers/media/i2c/ar0521.c
diff options
context:
space:
mode:
authorMarek Vasut <marex@denx.de>2022-08-24 01:22:16 +0300
committerMauro Carvalho Chehab <mchehab@kernel.org>2022-11-25 11:42:24 +0300
commit0958944a93058bfec7d9032518abd7d646009b17 (patch)
tree9c12c6b56d5baafc09c2d9d16c7725e985245627 /drivers/media/i2c/ar0521.c
parentc4cfd47eb4acefa593926c185db69eb56a0bc88b (diff)
downloadlinux-0958944a93058bfec7d9032518abd7d646009b17.tar.xz
media: mt9p031: Increase post-reset delay
The MT9P006 sensor driver sporadically fails to probe because the sensor responds with a NACK condition to I2C address on the bus during an attempt to read the sensor MT9P031_CHIP_VERSION register in mt9p031_registered(). Neither the MT9P006 nor MT9P031 datasheets are clear on reset signal timing. Older MT9M034 [1] datasheet provides those timing figures in Appendix-A and indicates it is necessary to wait 850000 EXTCLK cycles before starting any I2C communication. Add such a delay, which does make the sporadic I2C NACK go away, so it is likely similar constraint applies to this sensor. [1] https://www.onsemi.com/pdf/datasheet/mt9m034-d.pdf Signed-off-by: Marek Vasut <marex@denx.de> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'drivers/media/i2c/ar0521.c')
0 files changed, 0 insertions, 0 deletions