From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Tarang Raval <tarang.raval@siliconsignals.io>
Cc: "Shravan.Chippa@microchip.com" <Shravan.Chippa@microchip.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"kieran.bingham@ideasonboard.com"
<kieran.bingham@ideasonboard.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"umang.jain@ideasonboard.com" <umang.jain@ideasonboard.com>,
"zhi.mao@mediatek.com" <zhi.mao@mediatek.com>,
"julien.massot@collabora.com" <julien.massot@collabora.com>,
"mike.rudenko@gmail.com" <mike.rudenko@gmail.com>,
"benjamin.mugnier@foss.st.com" <benjamin.mugnier@foss.st.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] media: i2c: imx334: Convert to CCI register access helpers
Date: Tue, 11 Mar 2025 10:13:31 +0000 [thread overview]
Message-ID: <Z9AMywzmV97OycES@kekkonen.localdomain> (raw)
In-Reply-To: <PN3P287MB18297B36A79D3A1AD568448A8BD12@PN3P287MB1829.INDP287.PROD.OUTLOOK.COM>
Hi Tarang,
On Tue, Mar 11, 2025 at 10:05:12AM +0000, Tarang Raval wrote:
> Hi Sakari,
>
> > On Tue, Mar 11, 2025 at 06:51:48AM +0000, Shravan.Chippa@microchip.com wrote:
> > > Hi Laurent,
> > >
> > > > -----Original Message-----
> > > > From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > > Sent: Tuesday, March 11, 2025 12:09 PM
> > > > To: shravan Chippa - I35088 <Shravan.Chippa@microchip.com>
> > > > Cc: tarang.raval@siliconsignals.io; sakari.ailus@linux.intel.com;
> > > > kieran.bingham@ideasonboard.com; mchehab@kernel.org;
> > > > hverkuil@xs4all.nl; umang.jain@ideasonboard.com; zhi.mao@mediatek.com;
> > > > julien.massot@collabora.com; mike.rudenko@gmail.com;
> > > > benjamin.mugnier@foss.st.com; linux-media@vger.kernel.org; linux-
> > > > kernel@vger.kernel.org
> > > > Subject: Re: [PATCH 2/6] media: i2c: imx334: Convert to CCI register access
> > > > helpers
> > > >
> > > > EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> > > > content is safe
> > > >
> > > > Hi Shravan,
> > > >
> > > > On Tue, Mar 11, 2025 at 06:14:28AM +0000, Shravan.Chippa@microchip.com
> > > > wrote:
> > > > > Hi Tarang,
> > > > >
> > > > > Thanks for the patch series with CCI register access helpers on top of
> > > > > my patches I have tested (1080p,720p, 480p resolution only) and
> > > > > working on my board with small PLL changes to make it compatible with
> > > > > pfsoc board (mpfs-video-kit).
> > > >
> > > > Could you please provide more information about what those PLL changes are
> > > > ?
> > >
> > > Here is the change for mpfs-video-kit board.
> > >
> > > diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
> > > index 375367314416..30470dbd1f3c 100644
> > > --- a/drivers/media/i2c/imx334.c
> > > +++ b/drivers/media/i2c/imx334.c
> > > @@ -236,9 +236,9 @@ static const struct cci_reg_sequence common_mode_regs[] = {
> > > { IMX334_REG_XVS_XHS_OUTSEL, 0x20},
> > > { IMX334_REG_XVS_XHS_DRV, 0x0f},
> > > { IMX334_REG_BCWAIT_TIME, 0x3b},
> > > - { IMX334_REG_CPWAIT_TIME, 0x2a},
> > > + { IMX334_REG_CPWAIT_TIME, 0x29},
> >
> > A patch converting the driver to use V4L2 CCI / human-readable register
> > names should not change the values written.
>
> This change is not from my patch.
>
> You can recheck Shravan’s second patch, there is no change in the
> CPWAIT_TIME value from my patch or his.
>
> The change Shravan mentioned was made locally to ensure compatibility
> with the mpfs-video-kit board, as Laurent requested.
> That’s why he provided those details.
Right. I don't know what this or the other change do exactly, but
presumably the other one is a clock tree divider that reduces the link
frequency (or pixel rate in pixel array). That should be handled
separately.
--
Sakari Ailus
next prev parent reply other threads:[~2025-03-11 10:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:17 [PATCH 0/6] media: i2c: imx334: Miscellaneous cleanups and improvements Tarang Raval
2025-03-10 7:17 ` [PATCH 1/6] media: i2c: imx334: Simplify with dev_err_probe() Tarang Raval
2025-03-10 7:17 ` [PATCH 2/6] media: i2c: imx334: Convert to CCI register access helpers Tarang Raval
2025-03-11 6:14 ` Shravan.Chippa
2025-03-11 6:38 ` Laurent Pinchart
2025-03-11 6:51 ` Shravan.Chippa
2025-03-11 9:46 ` Sakari Ailus
2025-03-11 9:59 ` Shravan.Chippa
2025-03-11 10:05 ` Tarang Raval
2025-03-11 10:13 ` Sakari Ailus [this message]
2025-03-10 7:17 ` [PATCH 3/6] media: i2c: imx334: Remove redundant register entries Tarang Raval
2025-03-10 7:17 ` [PATCH 4/6] media: i2c: imx334: Support 4 or 8 lane operation modes Tarang Raval
2025-03-27 10:09 ` Sakari Ailus
2025-03-27 10:54 ` Tarang Raval
2025-03-27 14:32 ` Dave Stevenson
2025-03-27 15:38 ` Tarang Raval
2025-03-10 7:17 ` [PATCH 5/6] media: i2c: imx334: Fix power management and control handling Tarang Raval
2025-03-10 7:17 ` [PATCH 6/6] media: i2c: imx334: Enable runtime PM before sub-device registration Tarang Raval
2025-03-27 10:06 ` Sakari Ailus
2025-03-27 11:02 ` Tarang Raval
2025-03-27 11:14 ` 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=Z9AMywzmV97OycES@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=Shravan.Chippa@microchip.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=hverkuil@xs4all.nl \
--cc=julien.massot@collabora.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mike.rudenko@gmail.com \
--cc=tarang.raval@siliconsignals.io \
--cc=umang.jain@ideasonboard.com \
--cc=zhi.mao@mediatek.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