From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Bryan O'Donoghue <bod.linux@nxsw.ie>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@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>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v7 00/15] Add dt-bindings and dtsi changes for CAMSS on x1e80100 silicon
Date: Tue, 15 Jul 2025 16:08:18 +0300 [thread overview]
Message-ID: <f753f088-474b-41bb-82d3-6684bea2f87e@linaro.org> (raw)
In-Reply-To: <4281887a-e7c0-43bc-9e72-96f0e432c58f@nxsw.ie>
On 7/15/25 14:16, Bryan O'Donoghue wrote:
> On 15/07/2025 11:27, Vladimir Zapolskiy wrote:
>>>> 1. This is an incorrect assumption, unfortunately it was not discussed
>>>> previously for whatever reason, good news now it gets a discussion under
>>>> drivers/phy changeset.
>>> Perhaps you can explain why ?
>> It's quite easy, sensors are not connected to CSIDs. Moreover data flows
>> from any sensor can be processed on any CSID, there is no static hardware
>> links, which are attempted to be introduced.
>
> This statement is not correct.
Please elaborate, what statement above is not correct?
> The port@ in CAMSS pertains to the camss-csiphy device not to the
> camss-csid device, so there is no hard link to any specific CSID in the
> dts scheme here.
And here it's just a confirmation that my statement above is correct,
so please be consistent, and especially in any kind of accusations like
you've just given above.
Any of ports in CAMSS device tree are properties of CSIPHY IPs, and ports
are not the properties of CSID or whatever is left in CAMSS after the
extraction.
If CSIPHYs are extracted from CAMSS into its own device tree node, so all
CSIPHY only properties shall be removed from CAMSS, like CSIPHY reg,
interrupts, clocks and ports as well.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2025-07-15 13:08 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 12:57 [PATCH v7 00/15] Add dt-bindings and dtsi changes for CAMSS on x1e80100 silicon Bryan O'Donoghue
2025-07-11 12:57 ` [PATCH v7 01/15] dt-bindings: media: qcom,x1e80100-camss: Assign correct main register bank to first address Bryan O'Donoghue
2025-07-13 8:15 ` Krzysztof Kozlowski
2025-07-13 9:12 ` Bryan O'Donoghue
2025-07-13 9:34 ` Krzysztof Kozlowski
2025-07-14 6:41 ` Krzysztof Kozlowski
2025-07-11 12:57 ` [PATCH v7 02/15] dt-bindings: media: qcom,x1e80100-camss: Convert from inline PHY definitions to PHY handles Bryan O'Donoghue
2025-07-13 8:18 ` Krzysztof Kozlowski
2025-07-13 8:20 ` Krzysztof Kozlowski
2025-07-13 9:14 ` Bryan O'Donoghue
2025-07-13 9:39 ` Krzysztof Kozlowski
2025-07-13 9:48 ` Bryan O'Donoghue
2025-07-13 10:03 ` Krzysztof Kozlowski
2025-07-11 12:57 ` [PATCH v7 03/15] media: qcom: camss: Add legacy_phy flag to SoC definition structures Bryan O'Donoghue
2025-07-11 12:57 ` [PATCH v7 04/15] media: qcom: camss: Add support for PHY API devices Bryan O'Donoghue
2025-07-16 9:36 ` Loic Poulain
2025-07-16 10:59 ` Bryan O'Donoghue
2025-07-11 12:57 ` [PATCH v7 05/15] media: qcom: camss: Drop legacy PHY descriptions from x1e Bryan O'Donoghue
2025-07-11 12:57 ` [PATCH v7 06/15] arm64: dts: qcom: x1e80100: Add CAMCC block definition Bryan O'Donoghue
2025-07-11 12:57 ` [PATCH v7 07/15] arm64: dts: qcom: x1e80100: Add CCI definitions Bryan O'Donoghue
2025-07-11 12:58 ` [PATCH v7 08/15] arm64: dts: qcom: x1e80100: Add MIPI CSI PHY nodes Bryan O'Donoghue
2025-07-13 8:28 ` Krzysztof Kozlowski
2025-07-13 8:31 ` Krzysztof Kozlowski
2025-07-17 20:34 ` Konrad Dybcio
2025-07-11 12:58 ` [PATCH v7 09/15] arm64: dts: qcom: x1e80100: Add CAMSS block definition Bryan O'Donoghue
2025-07-11 12:58 ` [PATCH v7 10/15] arm64: dts: qcom: x1e80100-crd: Add pm8010 CRD pmic,id=m regulators Bryan O'Donoghue
2025-07-14 9:07 ` Konrad Dybcio
2025-07-11 12:58 ` [PATCH v7 11/15] arm64: dts: qcom: x1e80100-crd: Add ov08x40 RGB sensor on CSIPHY4 Bryan O'Donoghue
2025-07-14 13:28 ` Konrad Dybcio
2025-07-11 12:58 ` [PATCH v7 12/15] arm64: dts: qcom: x1e80100-t14s: Add pm8010 camera PMIC with voltage levels for IR and RGB camera Bryan O'Donoghue
2025-07-14 13:29 ` Konrad Dybcio
2025-07-11 12:58 ` [PATCH v7 13/15] arm64: dts: qcom: x1e80100-t14s: Add on ov02c10 RGB sensor on CSIPHY4 Bryan O'Donoghue
2025-07-11 12:58 ` [PATCH v7 14/15] arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add pm8010 camera PMIC with voltage levels for IR and RGB camera Bryan O'Donoghue
2025-07-11 12:58 ` [PATCH v7 15/15] arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add OV02E10 RGB sensor on CSIPHY4 Bryan O'Donoghue
2025-07-15 6:53 ` [PATCH v7 00/15] Add dt-bindings and dtsi changes for CAMSS on x1e80100 silicon Vladimir Zapolskiy
2025-07-15 7:01 ` Krzysztof Kozlowski
2025-07-15 7:19 ` Vladimir Zapolskiy
2025-07-15 7:46 ` Krzysztof Kozlowski
2025-07-15 8:48 ` Bryan O'Donoghue
2025-07-15 10:27 ` Vladimir Zapolskiy
2025-07-15 11:16 ` Bryan O'Donoghue
2025-07-15 13:08 ` Vladimir Zapolskiy [this message]
2025-07-15 13:22 ` Bryan O'Donoghue
2025-07-15 15:25 ` Vladimir Zapolskiy
2025-07-16 13:17 ` Bryan O'Donoghue
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=f753f088-474b-41bb-82d3-6684bea2f87e@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=andersson@kernel.org \
--cc=bod.linux@nxsw.ie \
--cc=bryan.odonoghue@linaro.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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mturquette@baylibre.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=todor.too@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).