From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/6] arm64: dts: qcom: sm8550-qrd: remove data-lanes property of image sensor
Date: Wed, 3 Dec 2025 13:57:37 +0200 [thread overview]
Message-ID: <5c163334-2ddd-4e52-8add-30652b34dc0f@linaro.org> (raw)
In-Reply-To: <94d6d26e-8009-437d-af9f-0a3c69fe8ed3@oss.qualcomm.com>
On 12/3/25 13:50, Konrad Dybcio wrote:
> On 12/3/25 12:41 PM, Vladimir Zapolskiy wrote:
>> On 12/3/25 13:11, Konrad Dybcio wrote:
>>> On 12/3/25 5:05 AM, Vladimir Zapolskiy wrote:
>>>> Samsung S5K3M5 image sensor supports only 4-lane MIPI CSI-2 interface,
>>>> which makes the sensor data-lanes property redundant, and it can be
>>>> safely removed from the board dts file. Noteworthy that the property
>>>> value is incorrect, because conventionally lanes enumeration of image
>>>> sensors starts from index 1.
>>>
>>> This seems to vary between sensors
>>>
>>
>> It should not, from Documentation/devicetree/bindings/media/video-interfaces.yaml
>> the clock lane has index 0, data lanes enumeration starts from 1:
>>
>> data-lanes:
>> ....
>> description:
>> An array of physical data lane indexes. Position of an entry determines
>> the logical lane number, while the value of an entry indicates physical
>> lane, e.g. for 2-lane MIPI CSI-2 bus we could have "data-lanes = <1 2>;",
>> assuming the clock lane is on hardware lane 0.
>
> I interpret the last sentence as ">>if<< the clock lane is 0, then data lanes
> start at 1. I'm not sure if the spec mandates that's the case though.
>
Well, that's the absolute common practice for media devices, which I'd like
to follow without a deviation from it or introducing a novation.
The dt bindings documentation of this S5K3M5 sensor device describes the value
of the optional data-lanes property accordingly:
https://lore.kernel.org/linux-media/20251203040241.71018-2-vladimir.zapolskiy@linaro.org/
So, I belive, this change under review should be fine as is.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2025-12-03 11:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 4:05 [PATCH 0/6] arm64: dts: qcom: sm8550-qrd/hdk: correct S5K3M5 properties Vladimir Zapolskiy
2025-12-03 4:05 ` [PATCH 1/6] arm64: dts: qcom: sm8550-qrd: rename image sensor supply properties Vladimir Zapolskiy
2025-12-03 11:09 ` Konrad Dybcio
2025-12-03 4:05 ` [PATCH 2/6] arm64: dts: qcom: sm8550-qrd: remove data-lanes property of image sensor Vladimir Zapolskiy
2025-12-03 11:11 ` Konrad Dybcio
2025-12-03 11:41 ` Vladimir Zapolskiy
2025-12-03 11:50 ` Konrad Dybcio
2025-12-03 11:57 ` Vladimir Zapolskiy [this message]
2025-12-05 13:17 ` Konrad Dybcio
2025-12-03 4:05 ` [PATCH 3/6] arm64: dts: qcom: sm8550-qrd: move camss status property to the end Vladimir Zapolskiy
2025-12-03 8:32 ` Krzysztof Kozlowski
2025-12-03 11:53 ` Vladimir Zapolskiy
2025-12-03 4:05 ` [PATCH 4/6] arm64: dts: qcom: sm8550-hdk-rear-camera-card: rename supply properties Vladimir Zapolskiy
2025-12-03 11:09 ` Konrad Dybcio
2025-12-03 4:05 ` [PATCH 5/6] arm64: dts: qcom: sm8550-hdk-rear-camera-card: remove optional property Vladimir Zapolskiy
2025-12-03 4:05 ` [PATCH 6/6] arm64: dts: qcom: sm8550-hdk-rear-camera-card: move camss status property Vladimir Zapolskiy
2025-12-03 8:32 ` Krzysztof Kozlowski
2025-12-03 12:02 ` Neil Armstrong
2025-12-03 17:40 ` Krzysztof Kozlowski
2025-12-03 8:25 ` [PATCH 0/6] arm64: dts: qcom: sm8550-qrd/hdk: correct S5K3M5 properties Neil Armstrong
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=5c163334-2ddd-4e52-8add-30652b34dc0f@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=neil.armstrong@linaro.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