summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorDave Stevenson <dave.stevenson@raspberrypi.com>2022-10-28 17:08:52 +0100
committerMauro Carvalho Chehab <mchehab@kernel.org>2022-11-25 06:51:50 +0000
commit6b2a01c90e277d46f99321e4a1f50ee08c04abba (patch)
treef3cf1945d8365f9781226e306e42e4bb1ea25dc5 /tools/perf/scripts/python
parent995809ce04a9e4c5c874b05fedd3a36b4285c2cd (diff)
downloadlinux-6b2a01c90e277d46f99321e4a1f50ee08c04abba.tar.gz
linux-6b2a01c90e277d46f99321e4a1f50ee08c04abba.zip
media: i2c: ov9282: Correct HTS register for configured pixel rate
The calculations from pixel rate, width+hblank, and height+vblank do not give the correct framerate - it's half the speed it should be. The datasheet lists the default for the TIMING_HTS registers (0x380c/d) as being 0x2d8 (728) which is less than the width of the image, so the units clearly can't be pixels. If TIMING_HTS is considered to be units of 2-pixels, then the resulting value of 0x5b0 (1456) makes all the calculations correct. This driver is reporting an HBLANK value of 250, with an image width of 1280, so TIMING_HTS is 1530 (0x5fa) pixels. However it was also setting the register to 0x5fa, thereby not taking into account it being units of 2-pixels. Correct the register value to 0x2fd so that all the timing calculations give the correct results. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com> Reviewed-by: Jacopo Mondi <jacopo@jmondi.org> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions