From: Nihal Kumar Gupta <quic_nihalkum@quicinc.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
<bryan.odonoghue@linaro.org>, <mchehab@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<hverkuil-cisco@xs4all.nl>, <cros-qcom-dts-watchers@chromium.org>,
<catalin.marinas@arm.com>, <will@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<quic_svankada@quicinc.com>, <linux-media@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Ravi Shankar <quic_rshankar@quicinc.com>,
Vishal Verma <quic_vishverm@quicinc.com>
Subject: Re: [PATCH v7 5/5] arm64: dts: qcom: monaco-evk-camera: Add DT overlay
Date: Wed, 17 Dec 2025 19:49:42 +0530 [thread overview]
Message-ID: <facbe87c-a2e1-4cc2-8dc1-30f716814588@quicinc.com> (raw)
In-Reply-To: <5bd29b5f-6fcf-428d-b451-698d92f0883e@linaro.org>
On 16-12-2025 13:05, Vladimir Zapolskiy wrote:
>> @@ -0,0 +1,67 @@
>> +// SPDX-License-Identifier: BSD-3-Clause
>> +/*
>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>
> Year is missing.
>
This is as per new yearless copyright format.
>> + */
>> +
>> +
>> + csiphy1_ep: endpoint {
>> + clock-lanes = <7>;
>
> Please remove 'clock-lanes' property here.
>
ACK
>> + data-lanes = <0 1 2 3>;
>> + remote-endpoint = <&imx577_ep1>;
>> + };
>> + };
>> + };
>> + imx577_ep1: endpoint {
>> + link-frequencies = /bits/ 64 <600000000>;
>> + data-lanes = <0 1 2 3>;
>
> data-lanes property value should be '1 2 3 4>', 0 is for the clock lane.
>
> On CAMSS side this cannot be changed, unfortunately it's a lingering issue.
>
So, I should set data-lanes = <1 2 3 4> in imx577_ep1, and keep csiphy1_ep as <0 1 2 3>, correct?
Is there a reason CAMSS side can’t change this? We should handle it properly in future targets.
>> + remote-endpoint = <&csiphy1_ep>;
>> + };
>> + };
>> + };
>> +};
>
> If only one of 3 defined from 4/5 regulators is used, do you really wish
> to describle all 3 in advance? You may consider to remove 2 currently unused
> GPIO controlled regulator descriptions, and squash this change with 4/5.
As discussed, we agreed to add support for other sensors: https://lore.kernel.org/all/4b73f64a-1e28-4f25-80d2-3d59575b9da2@oss.qualcomm.com
Regulator changes are in monaco-evk.dts, and sensor overlay changes are present in monaco-evk-camera-imx577.dtso
It’s better to keep these as separate patches rather than merging them into one.
--
Regards,
Nihal Kumar Gupta
next prev parent reply other threads:[~2025-12-17 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 6:22 [PATCH v7 0/5] Add CCI and imx577 sensor support for monaco evk Nihal Kumar Gupta
2025-12-16 6:22 ` [PATCH v7 1/5] dt-bindings: i2c: qcom-cci: Document qcs8300 compatible Nihal Kumar Gupta
2025-12-16 6:22 ` [PATCH v7 2/5] arm64: dts: qcom: monaco: Add CCI definitions Nihal Kumar Gupta
2025-12-16 6:22 ` [PATCH v7 3/5] arm64: dts: qcom: monaco: Add camera MCLK pinctrl Nihal Kumar Gupta
2025-12-16 7:21 ` Vladimir Zapolskiy
2025-12-17 11:12 ` Konrad Dybcio
2025-12-16 6:22 ` [PATCH v7 4/5] arm64: dts: qcom: monaco-evk: Add camera AVDD regulators Nihal Kumar Gupta
2025-12-17 11:14 ` Konrad Dybcio
2025-12-17 14:18 ` Nihal Kumar Gupta
2025-12-16 6:22 ` [PATCH v7 5/5] arm64: dts: qcom: monaco-evk-camera: Add DT overlay Nihal Kumar Gupta
2025-12-16 7:35 ` Vladimir Zapolskiy
2025-12-17 14:19 ` Nihal Kumar Gupta [this message]
2025-12-18 13:39 ` Konrad Dybcio
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=facbe87c-a2e1-4cc2-8dc1-30f716814588@quicinc.com \
--to=quic_nihalkum@quicinc.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_rshankar@quicinc.com \
--cc=quic_svankada@quicinc.com \
--cc=quic_vishverm@quicinc.com \
--cc=robh@kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=will@kernel.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