mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
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 v5 4/6] media: i2c: imx334: add default values in 3840x2160@60 array
Date: Fri, 25 Nov 2022 18:02:07 +0200	[thread overview]
Message-ID: <Y4Dm//xBeYBijT4d@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <20221125050807.1857479-5-shravan.chippa@microchip.com>

Hi Shravan,

On Fri, Nov 25, 2022 at 10:38:05AM +0530, shravan kumar wrote:
> From: Shravan Chippa <shravan.chippa@microchip.com>
> 
> -If we have only one mode there is no need to update camera
> reset(default) values when we initialize the camera

How is this related to the patch?

> 
> -If we have mutipull modes in this case we need all value to
> write while camera initializing, so i will not effect other modes
> while shifting dynamically
> 
> -All default values for 3840x2160@60 updated becouse if we change
> the mode we will not be able to recover the values, so add in
> mode_3840x2160_regs[] array

Please remove dashes in front of the paragrahs and use period in the end of
sentences.

Are these registers' values specific to this mode or are they different on
different modes?

> 
> Signed-off-by: Shravan Chippa <shravan.chippa@microchip.com>
> ---
>  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 d3bb62c162b3..cd41df56ab7d 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 */

-- 
Kind regards,

Sakari Ailus

  reply	other threads:[~2022-11-25 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  5:08 [PATCH v5 0/6] media: i2c: imx334: support lower bandwidth mode shravan kumar
2022-11-25  5:08 ` [PATCH v5 1/6] dt-bindings: imx334: modify link frequency in examples shravan kumar
2022-11-25 15:55   ` Sakari Ailus
2022-11-26 10:51     ` shravan kumar
2022-11-26 14:52       ` Sakari Ailus
2022-11-25  5:08 ` [PATCH v5 2/6] media: i2c: imx334: modify link frequency as for the configureation shravan kumar
2022-11-25  5:08 ` [PATCH v5 3/6] media: i2c: imx334: hblank set function modify shravan kumar
2022-11-25 15:58   ` Sakari Ailus
2022-11-25  5:08 ` [PATCH v5 4/6] media: i2c: imx334: add default values in 3840x2160@60 array shravan kumar
2022-11-25 16:02   ` Sakari Ailus [this message]
2022-11-26 10:58     ` shravan kumar
2022-11-25  5:08 ` [PATCH v5 5/6] media: i2c: imx334: support lower bandwidth mode shravan kumar
2022-11-25 16:15   ` Sakari Ailus
2022-11-25  5:08 ` [PATCH v5 6/6] media: i2c: imx334: updating pixel and link frequency shravan kumar

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=Y4Dm//xBeYBijT4d@valkosipuli.retiisi.eu \
    --to=sakari.ailus@iki.fi \
    --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®