You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The avt3_video_ops_s_frame_interval function clamps the frame rate using the FRAME_RATE_MIN/MAX registers. However, these values are not necessarily correct. The frame width/height/offset is not written to the sensor until a stream is started, so the frame rate min/max values are based on the previous frame size.
For example, I'm using the ALVIUM 1800 C-510m. On startup, the frame size is set to the maximum. I set the frame rate to 250 Hz, but the driver clamps the value to ~60 Hz. When I start the stream, the driver writes the 60 Hz frame rate into the sensor. If I stop the stream, set the frame rate again, and restart - I get the correct 250 Hz behavior.
The text was updated successfully, but these errors were encountered:
…o alvium csi2 driver
Merge in HSW_CSIDRIVER/alvium-csi2-driver from feature/UNISDK-4281-add-platform-abstraction-layer-to-alvium-csi2-driver to dev
* commit 'c6693b3e3a75fea93216bd8689bafbf4df32d4e7':
Added nvidia platform abstraction
Added initial version of platform abstraction layer
WIP: Add platform abstraction layer
The avt3_video_ops_s_frame_interval function clamps the frame rate using the FRAME_RATE_MIN/MAX registers. However, these values are not necessarily correct. The frame width/height/offset is not written to the sensor until a stream is started, so the frame rate min/max values are based on the previous frame size.
For example, I'm using the ALVIUM 1800 C-510m. On startup, the frame size is set to the maximum. I set the frame rate to 250 Hz, but the driver clamps the value to ~60 Hz. When I start the stream, the driver writes the 60 Hz frame rate into the sensor. If I stop the stream, set the frame rate again, and restart - I get the correct 250 Hz behavior.
The text was updated successfully, but these errors were encountered: