From: Neil Armstrong <neil.armstrong@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: qcom: sdm845-db845c-navigation-mezzanine: fix ov7251 lane properties
Date: Wed, 4 Dec 2024 13:16:46 +0100 [thread overview]
Message-ID: <0c1f4e6a-a77b-46d1-b944-9eb47d66556d@linaro.org> (raw)
In-Reply-To: <vlvchjynnwvevr2raosrwggwmjd5bdrs5skbsztskmzxjjdg7v@6qkhrjyaxlsz>
On 04/12/2024 12:05, Dmitry Baryshkov wrote:
> On Wed, Dec 04, 2024 at 11:56:54AM +0100, Neil Armstrong wrote:
>> Bindings documents data-lanes as a single entry with a separate
>> clock-lanes property, but DT uses 2 entries in data-lanes.
>>
>> This would suggest clock-lanes is missing, fix the DT using the
>> bindings example.
>>
>> This fixes:
>> sdm845-db845c-navigation-mezzanine.dtso: camera@60: port:endpoint:data-lanes: [0, 1] is too long
>> from schema $id: http://devicetree.org/schemas/media/i2c/ovti,ov7251.yaml#
>>
>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>> ---
>> arch/arm64/boot/dts/qcom/sdm845-db845c-navigation-mezzanine.dtso | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845-db845c-navigation-mezzanine.dtso b/arch/arm64/boot/dts/qcom/sdm845-db845c-navigation-mezzanine.dtso
>> index 0a87df806cafc8e726aacc07a772ca478d0ee3df..5a16f4c2b346b314af3d614266e1ca034057e643 100644
>> --- a/arch/arm64/boot/dts/qcom/sdm845-db845c-navigation-mezzanine.dtso
>> +++ b/arch/arm64/boot/dts/qcom/sdm845-db845c-navigation-mezzanine.dtso
>> @@ -115,7 +115,8 @@ camera@60 {
>>
>> port {
>> ov7251_ep: endpoint {
>> - data-lanes = <0 1>;
>> + clock-lanes = <1>;
>> + data-lanes = <0>;
>
> Is it really this way or the other way around, clock = <0>, data = <1>?
No idea actually, on the schematics the lanes from the DB845 are :
CSI0_P/N -> OV7251_CSI3_LANE0_P/N -> MIPI_CSI3_LANE0_P -> SoC
and
CLKP/N -> OV7251_CSI3_CLK_P/N -> MIPI_CSI3_CLK_P/N -> SoC
So I assume the data-lane is 0, for clock-lane I just used
the example, but I found nothing in the code using those assignments
Neil
>
>> /* remote-endpoint = <&csiphy3_ep>; */
>> };
>> };
>>
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2024-12-04 12:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 10:56 [PATCH 0/5] arm64: dts: qcom: misc DT bindings check fixes Neil Armstrong
2024-12-04 10:56 ` [PATCH 1/5] arm64: dts: qcom: qcm6490-shift-otter: remove invalid orientation-switch Neil Armstrong
2024-12-04 11:01 ` Dmitry Baryshkov
2024-12-04 10:56 ` [PATCH 2/5] arm64: dts: qcom: sdm845-db845c-navigation-mezzanine: fix ov7251 lane properties Neil Armstrong
2024-12-04 11:05 ` Dmitry Baryshkov
2024-12-04 12:16 ` Neil Armstrong [this message]
2024-12-04 13:10 ` Vladimir Zapolskiy
2024-12-04 13:16 ` neil.armstrong
2024-12-04 13:30 ` Vladimir Zapolskiy
2024-12-05 9:27 ` neil.armstrong
2024-12-05 9:31 ` Vladimir Zapolskiy
2024-12-04 10:56 ` [PATCH 3/5] arm64: dts: qcom: sc7180-trogdor-quackingstick: add missing avee-supply Neil Armstrong
2024-12-04 22:47 ` Doug Anderson
2024-12-04 10:56 ` [PATCH 4/5] arm64: dts: qcom: sc7180-trogdor-pompom: rename 5v-choke thermal zone Neil Armstrong
2024-12-04 11:06 ` Dmitry Baryshkov
2024-12-04 22:48 ` Doug Anderson
2024-12-04 10:56 ` [PATCH 5/5] arm64: dts: qcom: sc7180: fix psci power domain node names Neil Armstrong
2024-12-04 11:08 ` Dmitry Baryshkov
2024-12-04 22:49 ` Doug Anderson
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=0c1f4e6a-a77b-46d1-b944-9eb47d66556d@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®