HTS and VTS should be set via the V4L2_CID_VBLANK and V4L2_CID_HBLANK controls, which means that V4L2_CID_PIXEL_RATE also needs to be updated. All do come out of the ov5647_mode structure though.
The numbers are processed as described in https://www.kernel.org/doc/html/latest/ ... ra-sensors to set frame rate.
I'm not going to take the numbers in the driver as gospel as there was some debate over them whilst some patches were being upstreamed recently. https://lore.kernel.org/linux-media/202 ... board.com/
https://lore.kernel.org/linux-media/202 ... board.com/ (now merged upstream) says the pixel rate should be 58.333 MPix/s
0x3036 is 0x46 (70 decimal) in the current driver, and as above claims a pixel rate of 58.333MPix/s. If you're changing it to 0x66 / 102, then I'd expect the pixel rate to be 58.333 / 70 * 102 = 85MPix/s.
The configuration we had previously for 90fps set it to 0x69 (same as all the other modes), which would match the others at 87.5MHz.
Check all the values programmed using "v4l2-ctl --list-ctrls-menu -d /dev/v4l-subdev0" (on a Pi0-4, subdev2 on Pi5) to ensure they are the numbers expected, and that the frame rate then computes to the expected value.
You can't have 2 modes with the same resolution, so you have to update the current mode.
hts is currently badly named as it is actually the minimum and default values used.
vts is the default value only, so can be changed so that the default remains at 60fps but allows a lower value (down to OV5647_VBLANK_MIN of 24) to achieve higher frame rates.
The numbers are processed as described in https://www.kernel.org/doc/html/latest/ ... ra-sensors to set frame rate.
I'm not going to take the numbers in the driver as gospel as there was some debate over them whilst some patches were being upstreamed recently. https://lore.kernel.org/linux-media/202 ... board.com/
https://lore.kernel.org/linux-media/202 ... board.com/ (now merged upstream) says the pixel rate should be 58.333 MPix/s
0x3036 is 0x46 (70 decimal) in the current driver, and as above claims a pixel rate of 58.333MPix/s. If you're changing it to 0x66 / 102, then I'd expect the pixel rate to be 58.333 / 70 * 102 = 85MPix/s.
The configuration we had previously for 90fps set it to 0x69 (same as all the other modes), which would match the others at 87.5MHz.
Check all the values programmed using "v4l2-ctl --list-ctrls-menu -d /dev/v4l-subdev0" (on a Pi0-4, subdev2 on Pi5) to ensure they are the numbers expected, and that the frame rate then computes to the expected value.
You can't have 2 modes with the same resolution, so you have to update the current mode.
hts is currently badly named as it is actually the minimum and default values used.
vts is the default value only, so can be changed so that the default remains at 60fps but allows a lower value (down to OV5647_VBLANK_MIN of 24) to achieve higher frame rates.
Statistics: Posted by 6by9 — Mon Jan 12, 2026 12:11 pm