media: i2c: ov9282: Correct HTS register for configured pixel rate
authorDave Stevenson <dave.stevenson@raspberrypi.com>
Fri, 28 Oct 2022 16:08:52 +0000 (17:08 +0100)
committerMauro Carvalho Chehab <mchehab@kernel.org>
Fri, 25 Nov 2022 06:51:50 +0000 (06:51 +0000)
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>
drivers/media/i2c/ov9282.c

index 1524189..7e0b12b 100644 (file)
@@ -236,8 +236,8 @@ static const struct ov9282_reg mode_1280x720_regs[] = {
        {0x3809, 0x00},
        {0x380a, 0x02},
        {0x380b, 0xd0},
-       {0x380c, 0x05},
-       {0x380d, 0xfa},
+       {0x380c, 0x02},
+       {0x380d, 0xfd},
        {0x3810, 0x00},
        {0x3811, 0x08},
        {0x3812, 0x00},