summaryrefslogtreecommitdiffstats
path: root/include/media
diff options
context:
space:
mode:
authorJai Luthra <j-luthra@ti.com>2023-01-03 13:27:36 +0100
committerMauro Carvalho Chehab <mchehab@kernel.org>2023-02-06 08:29:10 +0100
commitd7ff69139908842adf824be4f50c7e9ac5886c04 (patch)
tree79aba188f9e0736fb653c172a52e44ca96792bd9 /include/media
parentdecea0a98b7ac04536c7d659f74783e8d67a06c0 (diff)
downloadlinux-d7ff69139908842adf824be4f50c7e9ac5886c04.tar.gz
linux-d7ff69139908842adf824be4f50c7e9ac5886c04.tar.bz2
linux-d7ff69139908842adf824be4f50c7e9ac5886c04.zip
media: ov5640: Handle delays when no reset_gpio set
Some module manufacturers [1][2] don't expose the RESETB and PWDN pins of the sensor directly through the 15-pin FFC connector. Instead wiring ~PWDN gpio to the sensor pins with appropriate delays. In such cases, reset_gpio will not be available to the driver, but it will still be toggled when the sensor is powered on, and thus we should still honor the wait time of >= 5ms + 1ms + 20ms (see figure 2-3 in [3]) before attempting any i/o operations over SCCB. Also, rename the function to ov5640_powerup_sequence to better match the datasheet (section 2.7). [1] https://digilent.com/reference/_media/reference/add-ons/pcam-5c/pcam_5c_sch.pdf [2] https://www.alinx.com/public/upload/file/AN5641_User_Manual.pdf [3] https://cdn.sparkfun.com/datasheets/Sensors/LightImaging/OV5640_datasheet.pdf Fixes: 19a81c1426c1 ("[media] add Omnivision OV5640 sensor driver") Reported-by: Nishanth Menon <nm@ti.com> Signed-off-by: Jai Luthra <j-luthra@ti.com> Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'include/media')
0 files changed, 0 insertions, 0 deletions