All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Acayan <mailingradian@gmail.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: 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>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Tianshu Qiu <tian.shu.qiu@intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	Robert Mader <robert.mader@collabora.com>,
	David Heidelberg <david@ixit.cz>,
	phone-devel@vger.kernel.org
Subject: Re: [PATCH v9 4/7] media: i2c: imx355: Restrict data lanes to 4
Date: Wed, 1 Apr 2026 21:06:06 -0400	[thread overview]
Message-ID: <ac3A_m4sKyJHa_hT@rdacayan> (raw)
In-Reply-To: <3c51f9fe-9c5f-47dd-a971-5b2a9e416230@linaro.org>

On Wed, Apr 01, 2026 at 12:37:14AM +0300, Vladimir Zapolskiy wrote:
> On 2/17/26 02:27, Richard Acayan wrote:
> > The IMX355 sensor driver currently supports having 4 data lanes. There
> > can't be more or less, so check if the firmware specifies 4 lanes.

This patch is superseded:

v10: https://lore.kernel.org/all/20260311020328.57976-1-mailingradian@gmail.com/
v11: https://lore.kernel.org/all/20260324020132.8683-5-mailingradian@gmail.com/

If my workflow somehow caused you not to receive the new versions,
please let me know.

> Does IMX355 sensor hardware support any other number of lanes?

Actually, I don't have hardware docs so I don't know. There can't be
more or less without driver support.

> 1) If no, then it makes no practical sense to check for data lanes number
> given by firmware, there can be any stored value, but it's known that the
> number of sensor data lanes is 4.
> 
> 2) If yes, then please return to the sensor dt bindings, and reflect any
> other options, right now it is set strictly to 4 lanes only.

I think more lane configurations in dt-bindings can be added as they are
discovered, either by reading hardware docs or by finding a board that
has a different number of lanes.

> In case if
> 'data-lanes' property is omitted, you can use 4 lanes as a default number
> of data lanes, and this information shall be documented in the dt bindings.

Later revisions of the patch require data-lanes.

  reply	other threads:[~2026-04-02  1:05 UTC|newest]

Thread overview: 23+ 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-03-31 21:22   ` Vladimir Zapolskiy
2026-04-28  3:52     ` Richard Acayan
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-03-31 21:37   ` Vladimir Zapolskiy
2026-04-02  1:06     ` Richard Acayan [this message]
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
2026-03-31  1:27           ` Richard Acayan
2026-03-31  7:02             ` Sakari Ailus
2026-03-31 19:44               ` Richard Acayan

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=ac3A_m4sKyJHa_hT@rdacayan \
    --to=mailingradian@gmail.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=mchehab@kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=rfoss@kernel.org \
    --cc=robert.mader@collabora.com \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.