From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: shravan kumar <shravan.chippa@microchip.com>
Cc: paul.j.murphy@intel.com, daniele.alessandrelli@intel.com,
mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 2/4] media: i2c: imx334: add missing reset values for mode 3840x2160_regs[]
Date: Fri, 13 Jan 2023 09:36:01 +0100 [thread overview]
Message-ID: <20230113083601.ctvydmuayeslo2b2@uno.localdomain> (raw)
In-Reply-To: <20230113010135.2620818-3-shravan.chippa@microchip.com>
Hi Shravan
On Fri, Jan 13, 2023 at 06:31:33AM +0530, shravan kumar wrote:
> From: Shravan Chippa <shravan.chippa@microchip.com>
>
> There are some missing reset reg_mode values for the 3840x2160@60
> resolution. The camera sensor still works in 3840x2160@60 resolution mode
> because of the register reset values. This is an issue when we change the
> modes dynamically. As an example, when we change the mode from 1920x1080@30
> resolution to 3840x2160@60 resoultion then the mode values will be written
^ rougue space
> to the registers from the array mode_3840x2160_regs[] which gives the wrong
> output which is incorrect resolution.
>
> So add the missing reset values to the mode_3840x2160_regs[].
>
> Signed-off-by: Shravan Chippa <shravan.chippa@microchip.com>
Not checking the register values as I don't have a datasheet
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Thanks
j
> ---
> drivers/media/i2c/imx334.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
> index ebacba3059b3..40ece08f20f5 100644
> --- a/drivers/media/i2c/imx334.c
> +++ b/drivers/media/i2c/imx334.c
> @@ -166,6 +166,7 @@ static const struct imx334_reg mode_3840x2160_regs[] = {
> {0x3288, 0x21},
> {0x328a, 0x02},
> {0x302c, 0x3c},
> + {0x302d, 0x00},
> {0x302e, 0x00},
> {0x302f, 0x0f},
> {0x3076, 0x70},
> @@ -240,7 +241,26 @@ static const struct imx334_reg mode_3840x2160_regs[] = {
> {0x3794, 0x7a},
> {0x3796, 0xa1},
> {0x3e04, 0x0e},
> + {0x319e, 0x00},
> {0x3a00, 0x01},
> + {0x3a18, 0xbf},
> + {0x3a19, 0x00},
> + {0x3a1a, 0x67},
> + {0x3a1b, 0x00},
> + {0x3a1c, 0x6f},
> + {0x3a1d, 0x00},
> + {0x3a1e, 0xd7},
> + {0x3a1f, 0x01},
> + {0x3a20, 0x6f},
> + {0x3a21, 0x00},
> + {0x3a22, 0xcf},
> + {0x3a23, 0x00},
> + {0x3a24, 0x6f},
> + {0x3a25, 0x00},
> + {0x3a26, 0xb7},
> + {0x3a27, 0x00},
> + {0x3a28, 0x5f},
> + {0x3a29, 0x00},
> };
>
> /* Supported sensor mode configurations */
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-01-13 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 1:01 [PATCH v9 0/4] media: i2c: imx334: support lower bandwidth mode shravan kumar
2023-01-13 1:01 ` [PATCH v9 1/4] media: i2c: imx334: replace __v4l2_ctrl_s_ctrl to __v4l2_ctrl_modify_range shravan kumar
2023-01-13 8:33 ` Jacopo Mondi
2023-01-13 1:01 ` [PATCH v9 2/4] media: i2c: imx334: add missing reset values for mode 3840x2160_regs[] shravan kumar
2023-01-13 8:36 ` Jacopo Mondi [this message]
2023-01-13 1:01 ` [PATCH v9 3/4] media: i2c: imx334: support lower bandwidth mode shravan kumar
2023-01-13 8:54 ` Jacopo Mondi
2023-01-13 1:01 ` [PATCH v9 4/4] media: i2c: imx334: update pixel and link frequency shravan kumar
2023-01-13 9:31 ` Jacopo Mondi
2023-01-14 11:37 ` Sakari Ailus
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=20230113083601.ctvydmuayeslo2b2@uno.localdomain \
--to=jacopo.mondi@ideasonboard.com \
--cc=daniele.alessandrelli@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@intel.com \
--cc=shravan.chippa@microchip.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®