From: Sakari Ailus <sakari.ailus@iki.fi>
To: shravan kumar <shravanmicrochip@gmail.com>
Cc: shravan kumar <shravan.chippa@microchip.com>,
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 1/6] dt-bindings: imx334: modify link frequency in examples
Date: Sat, 26 Nov 2022 16:52:36 +0200 [thread overview]
Message-ID: <Y4IoNGaPNzQ+fa7A@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <CAOPdzVa7Fb3Nwfs8ZzTLGJkJ6KMbqAs3KB6p-fu2jKVO0qNv4w@mail.gmail.com>
On Sat, Nov 26, 2022 at 04:21:57PM +0530, shravan kumar wrote:
> On Fri, Nov 25, 2022 at 9:27 PM Sakari Ailus <sakari.ailus@iki.fi> wrote:
> >
> > Hi Shravan,
> >
> > On Fri, Nov 25, 2022 at 10:38:02AM +0530, shravan kumar wrote:
> > > From: Shravan Chippa <shravan.chippa@microchip.com>
> > >
> > > -imx334 sensor is configured to 1782Mbps/lane for 3840x2160@60.
> > > -But in device tree bindings exapmple we are passing 891Mbps/lane
> > > so modified to 1782Mbps
> > >
> > > Signed-off-by: Shravan Chippa <shravan.chippa@microchip.com>
> > > ---
> > > Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml b/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml
> > > index f5055b9db693..ea3c93f97d65 100644
> > > --- a/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml
> > > +++ b/Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml
> > > @@ -82,7 +82,7 @@ examples:
> > > imx334: endpoint {
> > > remote-endpoint = <&cam>;
> > > data-lanes = <1 2 3 4>;
> > > - link-frequencies = /bits/ 64 <891000000>;
> > > + link-frequencies = /bits/ 64 <1782000000>;
> >
> > My understanding is that the original frequency is correct --- 594 MHz
> > pixel clock, 12 bpp, four lanes (and DDR).
>
> As per my understanding, other than these three parameters there is
> one more link frequency (communication frequency from imx334 sensor to
> MIPI CSI2 controller).
> thanks,
Feel free to add additional frequencies later on. But this patch appears to
be just wrong.
--
Sakari Ailus
next prev parent reply other threads:[~2022-11-26 14:52 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 [this message]
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
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=Y4IoNGaPNzQ+fa7A@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 \
--cc=shravanmicrochip@gmail.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®