public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: David Heidelberg <david@ixit.cz>
Cc: Richard Acayan <mailingradian@gmail.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Tianshu Qiu <tian.shu.qiu@intel.com>,
	Robert Mader <robert.mader@collabora.com>,
	phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v9 7/7] arm64: dts: qcom: sdm670-google-sargo: add imx355 front camera
Date: Tue, 24 Mar 2026 12:57:59 +0200	[thread overview]
Message-ID: <acJuN_FRqMTGgl8C@kekkonen.localdomain> (raw)
In-Reply-To: <eff25adf-c5fd-484d-a9ae-ec27c0d9c100@ixit.cz>

Hi David, Richard,

On Tue, Mar 24, 2026 at 10:35:24AM +0100, David Heidelberg wrote:
> 
> 
> On 24/03/2026 03:05, Richard Acayan wrote:
> > On Fri, Mar 13, 2026 at 07:26:47PM +0100, David Heidelberg wrote:
> > > On 17/02/2026 01:27, Richard Acayan wrote:
> > > [...]
> > > 
> > > > +&cci_i2c1 {
> > > > +	camera@1a {
> > > > +		compatible = "sony,imx355";
> > > > +		reg = <0x1a>;
> > > > +
> > > > +		clocks = <&camcc CAM_CC_MCLK2_CLK>;
> > > > +
> > > > +		assigned-clocks = <&camcc CAM_CC_MCLK2_CLK>;
> > > > +		assigned-clock-rates = <19200000>;
> > > 
> > > Extract from #sdm670-mainline:erebion.eu discussion:
> > > The imx355 can operate on 24 MHz (on both Pixel 3 and 3a), but Linux kernel
> > > driver can operate only with 19.2 MHz.
> > > 
> > > I assume it would be worth it mention at least by comment here.
> > 
> > This might set the series back because the devicetree isn't meant to be
> > written for specific software, but it's included in v11 because you
> > already asked twice.
> > 
> 
> I would say node with lower clock frequency is still much better than
> nothing or placeholder saying "i2c camera here". Instead we'll have small
> placeholder that value can be bumped to 24 MHz. Important is this can be
> easily improved when at least one consumer of the device-tree gains support.
> 
> We have very scarce support of cameras on mobile phones in mainline, thus
> leaving a comment that HW can do 24 MHz is reasonable compromise IMHO.

The bindings could document the supported frequency range.

In DTS it may make sense to set the frequency the vendor uses as it may
affect the link frequencies (albeit I guess they're the same in this
case?).

> 
> I personally got confused why Android sets higher clock, thus it may happen
> to other people looking at Pixel 3a as an example for their imx363 bring-up.
> 
> David
> 
> > The frequency could also be stated as having "better software support"
> > in general without mentioning Linux as the reason.
> 

-- 
Regards,

Sakari Ailus

      reply	other threads:[~2026-03-24 10:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  0:27 [PATCH v9 0/7] media: i2c: IMX355 for the Pixel 3a Richard Acayan
2026-02-17  0:27 ` [PATCH v9 1/7] dt-bindings: media: qcom,sdm670-camss: Remove clock-lanes requirement Richard Acayan
2026-02-17  7:38   ` Krzysztof Kozlowski
2026-02-17  0:27 ` [PATCH v9 2/7] dt-bindings: media: i2c: Add Sony IMX355 Richard Acayan
2026-02-17  0:27 ` [PATCH v9 3/7] media: i2c: imx355: Support devicetree and power management Richard Acayan
2026-02-17  0:27 ` [PATCH v9 4/7] media: i2c: imx355: Restrict data lanes to 4 Richard Acayan
2026-03-10  8:07   ` Sakari Ailus
2026-02-17  0:27 ` [PATCH v9 5/7] arm64: dts: qcom: sdm670: label the camss ports instead of endpoints Richard Acayan
2026-02-17  0:27 ` [PATCH v9 6/7] arm64: dts: qcom: sdm670: add camera mclk pins Richard Acayan
2026-02-17  0:27 ` [PATCH v9 7/7] arm64: dts: qcom: sdm670-google-sargo: add imx355 front camera Richard Acayan
2026-03-11  2:25   ` Richard Acayan
2026-03-11 19:59   ` David Heidelberg
2026-03-13 18:26   ` David Heidelberg
2026-03-24  2:05     ` Richard Acayan
2026-03-24  9:35       ` David Heidelberg
2026-03-24 10:57         ` Sakari Ailus [this message]

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=acJuN_FRqMTGgl8C@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mailingradian@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=rfoss@kernel.org \
    --cc=robert.mader@collabora.com \
    --cc=robh@kernel.org \
    --cc=tian.shu.qiu@intel.com \
    --cc=todor.too@gmail.com \
    --cc=vladimir.zapolskiy@linaro.org \
    /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