From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@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 09:48:51 +0100 [thread overview]
Message-ID: <ae0a309f-7e52-4d3c-8f26-989f22da5b07@linaro.org> (raw)
In-Reply-To: <9361e954-e2c9-41c6-be4c-12b0e4f367f5@linaro.org>
On 15/07/2025 07:53, Vladimir Zapolskiy wrote:
>> Finally I believe we should contine to have endpoints go from the
>> sensor
>> to CAMSS not the PHY as CAMSS' CSI decoder is the consumer of the data
>> not the PHY.
>>
>
> 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 ?
Taking the example of other setups similar to CAMSS I believe as laid
out above we should have
- Dedicated CSIPHY nodes
- Use the upstream PHY API
I believe individual CSIPHY nodes and endpoints from sensor to CSID are
more consistent with established upstream schema.
> 2. The whole new changes for legacy/new CSIPHY support is not present
> in v1-v6 of this changeset, it just appears out of nowhere in the v7,
> and since it is broken it should be removed from v8 expectedly.
Broken how though ?
> It's a pity to realize that instead of providing any review comments
> for the CSIPHY support series sent to you one month ago a lot of time
> is wastefully burnt on a broken by design change development.
I've been working on this on-and-off since the end of April:
Link:
https://lore.kernel.org/linux-media/c5cf0155-f839-4db9-b865-d39b56bb1e0a@linaro.org
The length of time isn't a good argument to apply a patch but, of course
its annoying.
The rationale here is:
- Follow existing examples and best practices [1][2][3]
- Minimize code bombs being generally conservative
in the amount of churn going in per release cycle
- Help people get changes merged - which can conflict with the
previous statement
Which from my reading of the state of the art means:
- Dedicated CSIPHY nodes
- Endpoints from sensor to CSI decoder
- And picking up on point #2 above minimizing the churn
[1] Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
[2] Documentation/devicetree/bindings/phy/mediatek,mt8365-csi-rx.yaml
[3]
https://lore.kernel.org/linux-media/20240220-rk3568-vicap-v9-12-ace1e5cc4a82@collabora.com/
---
bod
next prev parent reply other threads:[~2025-07-15 8:48 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 [this message]
2025-07-15 10:27 ` Vladimir Zapolskiy
2025-07-15 11:16 ` Bryan O'Donoghue
2025-07-15 13:08 ` Vladimir Zapolskiy
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=ae0a309f-7e52-4d3c-8f26-989f22da5b07@linaro.org \
--to=bryan.odonoghue@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=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 \
--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;
as well as URLs for NNTP newsgroup(s).