From: shravan kumar <shravan.chippa@microchip.com>
To: <paul.j.murphy@intel.com>, <daniele.alessandrelli@intel.com>,
<mchehab@kernel.org>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Shravan Chippa" <shravan.chippa@microchip.com>
Subject: [PATCH v5 2/6] media: i2c: imx334: modify link frequency as for the configureation
Date: Fri, 25 Nov 2022 10:38:03 +0530 [thread overview]
Message-ID: <20221125050807.1857479-3-shravan.chippa@microchip.com> (raw)
In-Reply-To: <20221125050807.1857479-1-shravan.chippa@microchip.com>
From: Shravan Chippa <shravan.chippa@microchip.com>
-Imx334 camera is configured for 1782Mbps/lane for 3840x2160@60
resolution. but the imx334_parse_hw_config() function comparing with
IMX334_LINK_FREQ(891Mbpa/lane) link frequency
-The 3840x2160@60 mode values for 1782Mbps/lane
-Updated Macro IMX334_LINK_FREQ to 1782Mbps/lane
-The same value is populated in the userspce also
Signed-off-by: Shravan Chippa <shravan.chippa@microchip.com>
---
drivers/media/i2c/imx334.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
index 7b0a9086447d..acc9f9f15e47 100644
--- a/drivers/media/i2c/imx334.c
+++ b/drivers/media/i2c/imx334.c
@@ -49,7 +49,7 @@
#define IMX334_INCLK_RATE 24000000
/* CSI2 HW configuration */
-#define IMX334_LINK_FREQ 891000000
+#define IMX334_LINK_FREQ 1782000000
#define IMX334_NUM_DATA_LANES 4
#define IMX334_REG_MIN 0x00
--
2.34.1
next prev parent reply other threads:[~2022-11-25 5:08 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 ` shravan kumar [this message]
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
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=20221125050807.1857479-3-shravan.chippa@microchip.com \
--to=shravan.chippa@microchip.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 \
/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®