[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z9AMywzmV97OycES@kekkonen.localdomain>
Date: Tue, 11 Mar 2025 10:13:31 +0000
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Tarang Raval <tarang.raval@...iconsignals.io>
Cc: "Shravan.Chippa@...rochip.com" <Shravan.Chippa@...rochip.com>,
"laurent.pinchart@...asonboard.com" <laurent.pinchart@...asonboard.com>,
"kieran.bingham@...asonboard.com" <kieran.bingham@...asonboard.com>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"hverkuil@...all.nl" <hverkuil@...all.nl>,
"umang.jain@...asonboard.com" <umang.jain@...asonboard.com>,
"zhi.mao@...iatek.com" <zhi.mao@...iatek.com>,
"julien.massot@...labora.com" <julien.massot@...labora.com>,
"mike.rudenko@...il.com" <mike.rudenko@...il.com>,
"benjamin.mugnier@...s.st.com" <benjamin.mugnier@...s.st.com>,
"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/6] media: i2c: imx334: Convert to CCI register access
helpers
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@...rochip.com wrote:
> > > Hi Laurent,
> > >
> > > > -----Original Message-----
> > > > From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> > > > Sent: Tuesday, March 11, 2025 12:09 PM
> > > > To: shravan Chippa - I35088 <Shravan.Chippa@...rochip.com>
> > > > Cc: tarang.raval@...iconsignals.io; sakari.ailus@...ux.intel.com;
> > > > kieran.bingham@...asonboard.com; mchehab@...nel.org;
> > > > hverkuil@...all.nl; umang.jain@...asonboard.com; zhi.mao@...iatek.com;
> > > > julien.massot@...labora.com; mike.rudenko@...il.com;
> > > > benjamin.mugnier@...s.st.com; linux-media@...r.kernel.org; linux-
> > > > kernel@...r.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@...rochip.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
Powered by blists - more mailing lists