From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Umang Jain <umang.jain@ideasonboard.com>, linux-media@vger.kernel.org
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
open list <linux-kernel@vger.kernel.org>,
Umang Jain <umang.jain@ideasonboard.com>
Subject: Re: [PATCH 4/5] media: imx335: Fix active area height discrepency
Date: Wed, 06 Mar 2024 17:05:13 +0000 [thread overview]
Message-ID: <170974471357.362031.9683522744235199514@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <20240306081038.212412-5-umang.jain@ideasonboard.com>
Quoting Umang Jain (2024-03-06 08:10:37)
> The imx335 reports a recommended pixel area of - 2592x1944.
> The driver supported mode however limits it to height=1940.
Hrm, I think I would convert widths and sizes to decimal as a patch
before this patch so the effect is clearer in this diff.
> Fix the height discrepency by correctly the value of height
> (with updates to vblank and mode registers).
>
> Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
> ---
> drivers/media/i2c/imx335.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/media/i2c/imx335.c b/drivers/media/i2c/imx335.c
> index 6ea09933e47b..c00e0c2be3f3 100644
> --- a/drivers/media/i2c/imx335.c
> +++ b/drivers/media/i2c/imx335.c
> @@ -246,13 +246,13 @@ static const int imx335_tpg_val[] = {
> };
>
> /* Sensor mode registers */
> -static const struct cci_reg_sequence mode_2592x1940_regs[] = {
> +static const struct cci_reg_sequence mode_2592x1944_regs[] = {
> {IMX335_REG_MODE_SELECT, 0x01},
> {IMX335_REG_MASTER_MODE, 0x00},
> - {IMX335_REG_WINMODE, 0x04},
> - {IMX335_REG_HTRIMMING_START, 0x0180},
> + {IMX335_REG_WINMODE, 0x00},
What's the distinction of the winmode here. What is 0x04 vs 0x00?
Is this something that could be a defined value? Or is that not worth
the effort?
> + {IMX335_REG_HTRIMMING_START, 0x30},
HTRIMMING_START has moved a lot more than I would expect there.
Is there a visual impact of any concern here?
> {IMX335_REG_HNUM, 0x0a20},
> - {IMX335_REG_Y_OUT_SIZE, 0x0794},
> + {IMX335_REG_Y_OUT_SIZE, 0x0798},
This bit looks expected ;-)
> {IMX335_REG_VCROP_POS, 0x00b0},
> {IMX335_REG_VCROP_SIZE, 0x0f58},
0x0f58 = 3928. Does that correspond to anything on the pixel array size?
We're modifying the vertical size, so I'm curious if the 'vcrop' is or
should be impacted?
> {IMX335_REG_OPB_SIZE_V, 0x00},
> @@ -403,14 +403,14 @@ static const u32 imx335_mbus_codes[] = {
> /* Supported sensor mode configurations */
> static const struct imx335_mode supported_mode = {
> .width = 2592,
> - .height = 1940,
> + .height = 1944,
> .hblank = 342,
> - .vblank = 2560,
> - .vblank_min = 2560,
> + .vblank = 2556,
> + .vblank_min = 2556,
> .vblank_max = 133060,
> .reg_list = {
> - .num_of_regs = ARRAY_SIZE(mode_2592x1940_regs),
> - .regs = mode_2592x1940_regs,
> + .num_of_regs = ARRAY_SIZE(mode_2592x1944_regs),
> + .regs = mode_2592x1944_regs,
> },
> };
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-03-06 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 8:10 [PATCH 0/5] media: imx335: 2/4 lane ops and improvements Umang Jain
2024-03-06 8:10 ` [PATCH 1/5] media: imx335: Support 2 or 4 lane operation modes Umang Jain
2024-03-06 16:42 ` Dave Stevenson
2024-03-08 5:37 ` Umang Jain
2024-03-06 17:06 ` Sakari Ailus
2024-03-08 18:44 ` kernel test robot
2024-03-08 20:31 ` kernel test robot
2024-03-08 20:51 ` kernel test robot
2024-03-06 8:10 ` [PATCH 2/5] media: imx335: Parse fwnode properties Umang Jain
2024-03-06 8:10 ` [PATCH 3/5] media: imx335: Use V4L2 CCI for accessing sensor registers Umang Jain
2024-03-06 16:55 ` Kieran Bingham
2024-03-08 22:36 ` kernel test robot
2024-03-06 8:10 ` [PATCH 4/5] media: imx335: Fix active area height discrepency Umang Jain
2024-03-06 17:05 ` Kieran Bingham [this message]
2024-03-06 17:17 ` Umang Jain
2024-03-06 8:10 ` [PATCH 5/5] media: imx335: Limit analogue gain value Umang Jain
2024-03-06 16:59 ` Kieran Bingham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170974471357.362031.9683522744235199514@ping.linuxembedded.co.uk \
--to=kieran.bingham@ideasonboard.com \
--cc=eagle.alexander923@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=umang.jain@ideasonboard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®