diff options
| author | Hans de Goede <johannes.goede@oss.qualcomm.com> | 2025-12-30 18:03:09 +0100 |
|---|---|---|
| committer | Hans Verkuil <hverkuil+cisco@kernel.org> | 2026-01-14 23:33:04 +0100 |
| commit | 46c96eec9a763813e4592d72ecb38a6a33113258 (patch) | |
| tree | 323b49a1c5f9ae5db7161f54742439addbd84ce3 /tools/lib/python/kdoc | |
| parent | ceb485b3378bf59d3ed23726e9effff9c2d6792d (diff) | |
| download | linux-46c96eec9a763813e4592d72ecb38a6a33113258.tar.gz linux-46c96eec9a763813e4592d72ecb38a6a33113258.zip | |
media: mt9m114: Drop start-, stop-streaming sequence from initialize
Drop the start-, stop-streaming sequence from initialize.
When streaming is started with a runtime-suspended sensor,
mt9m114_start_streaming() will runtime-resume the sensor which calls
mt9m114_initialize() immediately followed by calling
mt9m114_set_state(ENTER_CONFIG_CHANGE).
This results in the following state changes in quick succession:
mt9m114_set_state(ENTER_CONFIG_CHANGE) -> transitions to STREAMING
mt9m114_set_state(ENTER_SUSPEND) -> transitions to SUSPENDED
mt9m114_set_state(ENTER_CONFIG_CHANGE) -> transitions to STREAMING
these quick state changes confuses the CSI receiver on atomisp devices
causing streaming to not work.
Drop the state changes from mt9m114_initialize() and move
the mt9m114_initialize() call to mt9m114_start_streaming()
so that only a single mt9m114_set_state(ENTER_CONFIG_CHANGE) call
is made when streaming is started with a runtime-suspend sensor.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Hans Verkuil <hverkuil+cisco@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc')
0 files changed, 0 insertions, 0 deletions
