Re: [PATCH v2] media: ov5670: Fix incorrect frame timing reported to user

2017-08-10 Thread Sakari Ailus
On Thu, Aug 10, 2017 at 04:00:05PM +0900, Tomasz Figa wrote:
> Hi Chiranjeevi,
> 
> On Thu, Aug 10, 2017 at 6:59 AM, Chiranjeevi Rapolu
>  wrote:
> > Previously, pixel-rate/(pixels-per-line * lines-per-frame) was
> > yielding incorrect frame timing for the user.
> >
> > OV sensor is using internal timing and this requires
> > conversion (internal timing -> PPL) for correct HBLANK calculation.
> >
> > Now, change pixels-per-line domain from internal sensor clock to
> > pixels domain. Set HBLANK read-only because fixed PPL is used for all
> > resolutions. And, use more accurate link-frequency 422.4MHz instead of
> > rounding down to 420MHz.
> >
> > Signed-off-by: Chiranjeevi Rapolu 
> > ---
> > Changes in v2:
> > - Change subject to reflect frame timing info.
> > - Change OV5670_DEF_PPL so that it doesn't convey a register default
> >   value. And, add more comments to it.
> >  drivers/media/i2c/ov5670.c | 45 
> > +++--
> >  1 file changed, 23 insertions(+), 22 deletions(-)
> 
> Okay, the numbers in this version finally make sense. Thanks for
> figuring this out.
> 
> Reviewed-by: Tomasz Figa 

Thanks, applied!

-- 
Sakari Ailus
e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk


Re: [PATCH v2] media: ov5670: Fix incorrect frame timing reported to user

2017-08-10 Thread Tomasz Figa
Hi Chiranjeevi,

On Thu, Aug 10, 2017 at 6:59 AM, Chiranjeevi Rapolu
 wrote:
> Previously, pixel-rate/(pixels-per-line * lines-per-frame) was
> yielding incorrect frame timing for the user.
>
> OV sensor is using internal timing and this requires
> conversion (internal timing -> PPL) for correct HBLANK calculation.
>
> Now, change pixels-per-line domain from internal sensor clock to
> pixels domain. Set HBLANK read-only because fixed PPL is used for all
> resolutions. And, use more accurate link-frequency 422.4MHz instead of
> rounding down to 420MHz.
>
> Signed-off-by: Chiranjeevi Rapolu 
> ---
> Changes in v2:
> - Change subject to reflect frame timing info.
> - Change OV5670_DEF_PPL so that it doesn't convey a register default
>   value. And, add more comments to it.
>  drivers/media/i2c/ov5670.c | 45 +++--
>  1 file changed, 23 insertions(+), 22 deletions(-)

Okay, the numbers in this version finally make sense. Thanks for
figuring this out.

Reviewed-by: Tomasz Figa 

Best regards,
Tomasz


[PATCH v2] media: ov5670: Fix incorrect frame timing reported to user

2017-08-09 Thread Chiranjeevi Rapolu
Previously, pixel-rate/(pixels-per-line * lines-per-frame) was
yielding incorrect frame timing for the user.

OV sensor is using internal timing and this requires
conversion (internal timing -> PPL) for correct HBLANK calculation.

Now, change pixels-per-line domain from internal sensor clock to
pixels domain. Set HBLANK read-only because fixed PPL is used for all
resolutions. And, use more accurate link-frequency 422.4MHz instead of
rounding down to 420MHz.

Signed-off-by: Chiranjeevi Rapolu 
---
Changes in v2:
- Change subject to reflect frame timing info.
- Change OV5670_DEF_PPL so that it doesn't convey a register default
  value. And, add more comments to it.
 drivers/media/i2c/ov5670.c | 45 +++--
 1 file changed, 23 insertions(+), 22 deletions(-)

diff --git a/drivers/media/i2c/ov5670.c b/drivers/media/i2c/ov5670.c
index 8d8e16c..b9d4dd2 100644
--- a/drivers/media/i2c/ov5670.c
+++ b/drivers/media/i2c/ov5670.c
@@ -37,7 +37,13 @@
 
 /* horizontal-timings from sensor */
 #define OV5670_REG_HTS 0x380c
-#define OV5670_DEF_PPL 3360/* Default pixels per line */
+
+/*
+ * Pixels-per-line(PPL) = Time-per-line * pixel-rate
+ * In OV5670, Time-per-line = HTS/SCLK.
+ * HTS is fixed for all resolutions, not recommended to change.
+ */
+#define OV5670_FIXED_PPL   2724/* Pixels per line */
 
 /* Exposure controls from sensor */
 #define OV5670_REG_EXPOSURE0x3500
@@ -1705,12 +1711,12 @@ struct ov5670_mode {
 };
 
 /* Supported link frequencies */
-#define OV5670_LINK_FREQ_420MHZ42000
-#define OV5670_LINK_FREQ_420MHZ_INDEX  0
+#define OV5670_LINK_FREQ_422MHZ42240
+#define OV5670_LINK_FREQ_422MHZ_INDEX  0
 static const struct ov5670_link_freq_config link_freq_configs[] = {
{
/* pixel_rate = link_freq * 2 * nr_of_lanes / bits_per_sample */
-   .pixel_rate = (OV5670_LINK_FREQ_420MHZ * 2 * 2) / 10,
+   .pixel_rate = (OV5670_LINK_FREQ_422MHZ * 2 * 2) / 10,
.reg_list = {
.num_of_regs = ARRAY_SIZE(mipi_data_rate_840mbps),
.regs = mipi_data_rate_840mbps,
@@ -1719,7 +1725,7 @@ struct ov5670_mode {
 };
 
 static const s64 link_freq_menu_items[] = {
-   OV5670_LINK_FREQ_420MHZ
+   OV5670_LINK_FREQ_422MHZ
 };
 
 /*
@@ -1736,7 +1742,7 @@ struct ov5670_mode {
.num_of_regs = ARRAY_SIZE(mode_2592x1944_regs),
.regs = mode_2592x1944_regs,
},
-   .link_freq_index = OV5670_LINK_FREQ_420MHZ_INDEX,
+   .link_freq_index = OV5670_LINK_FREQ_422MHZ_INDEX,
},
{
.width = 1296,
@@ -1746,7 +1752,7 @@ struct ov5670_mode {
.num_of_regs = ARRAY_SIZE(mode_1296x972_regs),
.regs = mode_1296x972_regs,
},
-   .link_freq_index = OV5670_LINK_FREQ_420MHZ_INDEX,
+   .link_freq_index = OV5670_LINK_FREQ_422MHZ_INDEX,
},
{
.width = 648,
@@ -1756,7 +1762,7 @@ struct ov5670_mode {
.num_of_regs = ARRAY_SIZE(mode_648x486_regs),
.regs = mode_648x486_regs,
},
-   .link_freq_index = OV5670_LINK_FREQ_420MHZ_INDEX,
+   .link_freq_index = OV5670_LINK_FREQ_422MHZ_INDEX,
},
{
.width = 2560,
@@ -1766,7 +1772,7 @@ struct ov5670_mode {
.num_of_regs = ARRAY_SIZE(mode_2560x1440_regs),
.regs = mode_2560x1440_regs,
},
-   .link_freq_index = OV5670_LINK_FREQ_420MHZ_INDEX,
+   .link_freq_index = OV5670_LINK_FREQ_422MHZ_INDEX,
},
{
.width = 1280,
@@ -1776,7 +1782,7 @@ struct ov5670_mode {
.num_of_regs = ARRAY_SIZE(mode_1280x720_regs),
.regs = mode_1280x720_regs,
},
-   .link_freq_index = OV5670_LINK_FREQ_420MHZ_INDEX,
+   .link_freq_index = OV5670_LINK_FREQ_422MHZ_INDEX,
},
{
.width = 640,
@@ -1786,7 +1792,7 @@ struct ov5670_mode {
.num_of_regs = ARRAY_SIZE(mode_640x360_regs),
.regs = mode_640x360_regs,
},
-   .link_freq_index = OV5670_LINK_FREQ_420MHZ_INDEX,
+   .link_freq_index = OV5670_LINK_FREQ_422MHZ_INDEX,
}
 };
 
@@ -2016,13 +2022,6 @@ static int ov5670_set_ctrl(struct v4l2_ctrl *ctrl)
   OV5670_REG_VALUE_16BIT,
   ov5670->cur_mode->height + ctrl->val);
break;
-   case V4L2_CID_HBLANK:
-   /* Update HTS that meets expected horizontal blanking */
-   ret = ov5670_write_reg(ov5670, OV5670_REG_HTS,
-