Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: 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>,
	Vladimir Zapolskiy <vladimir.zapolskiy@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
Cc: Robert Mader <robert.mader@collabora.com>,
	David Heidelberg <david@ixit.cz>,
	phone-devel@vger.kernel.org
Subject: Re: [PATCH v8 1/7] dt-bindings: media: qcom,sdm670-camss: Remove clock-lanes property
Date: Tue, 10 Feb 2026 13:16:15 +0000	[thread overview]
Message-ID: <416e2f12-92c1-4e41-bf08-860443710035@linaro.org> (raw)
In-Reply-To: <20260210020207.10246-2-mailingradian@gmail.com>

On 10/02/2026 02:02, Richard Acayan wrote:
> The clock-lanes property has no effect on the hardware configuration, as
> of 336136e197e2 ("media: dt-bindings: media: camss: Remove clock-lane
> property"). Remove the clock-lanes property.
> 
> Suggested-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> Link: https://lore.kernel.org/r/bbf0dcd9-d0f2-49a6-a2f2-6ec9376f2f59@linaro.org
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> ---
>   .../bindings/media/qcom,sdm670-camss.yaml           | 13 -------------
>   1 file changed, 13 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml b/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
> index 35c40fe22376..78b9e03da06b 100644
> --- a/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
> +++ b/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
> @@ -116,15 +116,11 @@ properties:
>               unevaluatedProperties: false
>   
>               properties:
> -              clock-lanes:
> -                maxItems: 1
> -
>                 data-lanes:
>                   minItems: 1
>                   maxItems: 4
>   
>               required:
> -              - clock-lanes
>                 - data-lanes
>   
>         port@1:
> @@ -139,15 +135,11 @@ properties:
>               unevaluatedProperties: false
>   
>               properties:
> -              clock-lanes:
> -                maxItems: 1
> -
>                 data-lanes:
>                   minItems: 1
>                   maxItems: 4
>   
>               required:
> -              - clock-lanes
>                 - data-lanes
>   
>         port@2:
> @@ -162,15 +154,11 @@ properties:
>               unevaluatedProperties: false
>   
>               properties:
> -              clock-lanes:
> -                maxItems: 1
> -
>                 data-lanes:
>                   minItems: 1
>                   maxItems: 4
>   
>               required:
> -              - clock-lanes
>                 - data-lanes
>   
>   required:
> @@ -308,7 +296,6 @@ examples:
>                       reg = <0>;
>   
>                       csiphy_ep0: endpoint {
> -                        clock-lanes = <7>;
>                           data-lanes = <0 1 2 3>;
>                           remote-endpoint = <&front_sensor_ep>;
>                       };

I think the ask was to have clock-lanes in the board dts rather than 
dropping the clock-lanes from the yaml.

We want to keep clock-lanes in general as some SoCs support changing the 
lane assignment.

---
bod

  parent reply	other threads:[~2026-02-10 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  2:01 [PATCH v8 0/7] media: i2c: IMX355 for the Pixel 3a Richard Acayan
2026-02-10  2:02 ` [PATCH v8 1/7] dt-bindings: media: qcom,sdm670-camss: Remove clock-lanes property Richard Acayan
2026-02-10  9:16   ` Krzysztof Kozlowski
2026-02-10 12:38   ` Vladimir Zapolskiy
2026-02-10 13:16   ` Bryan O'Donoghue [this message]
2026-02-10  2:02 ` [PATCH v8 2/7] dt-bindings: media: i2c: Add Sony IMX355 Richard Acayan
2026-02-10  2:02 ` [PATCH v8 3/7] media: i2c: imx355: Support devicetree and power management Richard Acayan
2026-02-10  2:02 ` [PATCH v8 5/7] arm64: dts: qcom: sdm670: label the camss ports instead of endpoints Richard Acayan
2026-02-10  2:02 ` [PATCH v8 6/7] arm64: dts: qcom: sdm670: add camera mclk pins Richard Acayan
2026-02-10  2:02 ` [PATCH v8 7/7] arm64: dts: qcom: sdm670-google-sargo: add imx355 front camera Richard Acayan
2026-02-11  0:21 ` [PATCH v8 0/7] media: i2c: IMX355 for the Pixel 3a Richard Acayan
2026-02-13  6:29   ` Vladimir Zapolskiy

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=416e2f12-92c1-4e41-bf08-860443710035@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=andersson@kernel.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox