From: Neil Armstrong <neil.armstrong@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Conor Dooley <conor+dt@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 09/10] [RFT] arm64: dts: qcom: sm8250: extend CAMSS with new CSIPHY subdevices
Date: Mon, 23 Jun 2025 11:31:48 +0200 [thread overview]
Message-ID: <bed8c29c-1365-4005-aac7-1635a28295bf@linaro.org> (raw)
In-Reply-To: <20250612011531.2923701-10-vladimir.zapolskiy@linaro.org>
On 12/06/2025 03:15, Vladimir Zapolskiy wrote:
> Following the new device tree bindings for CAMSS IPs introduce csiphy2
> device tree node under SM8250 CAMSS, which allows to perform camera
> tests of the model on an RB5 board with an attached vision mezzanine.
>
> Note that the optional 'phys' property is deliberately not added.
>
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> ---
> For testing only, do not merge.
>
> arch/arm64/boot/dts/qcom/sm8250.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> index f0d18fd37aaf..401a32679580 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> @@ -4613,6 +4613,10 @@ camss: camss@ac6a000 {
> "cam_sf_0_mnoc",
> "cam_sf_icp_mnoc";
>
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> ports {
> #address-cells = <1>;
> #size-cells = <0>;
> @@ -4641,6 +4645,16 @@ port@5 {
> reg = <5>;
> };
> };
> +
> + csiphy2: phy@ac6e000 {
> + compatible = "qcom,csiphy";
> + reg = <0 0x0ac6e000 0 0x1000>;
> + clocks = <&camcc CAM_CC_CSIPHY2_CLK>,
> + <&camcc CAM_CC_CSI2PHYTIMER_CLK>;
> + clock-names = "csiphy", "csiphy_timer";
> + interrupts = <GIC_SPI 479 IRQ_TYPE_EDGE_RISING>;
> + #phy-cells = <0>;
> + };
I would've expected the CSI PHY nodes to be out of the camss node, why would you
keep them as subnodes since you would reference them via phys phandles ?
Neil
> };
>
> camcc: clock-controller@ad00000 {
next prev parent reply other threads:[~2025-06-23 9:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 1:15 [PATCH 00/10] media: qcom: camss: add support for csiphy devices Vladimir Zapolskiy
2025-06-12 1:15 ` [PATCH 01/10] media: qcom: camss: remove never used camss_vfe_get()/camss_vfe_put() Vladimir Zapolskiy
2025-06-12 7:31 ` Bryan O'Donoghue
2025-06-12 1:15 ` [PATCH 02/10] media: qcom: camss: remove subdev resource argument from msm_csiphy_subdev_init() Vladimir Zapolskiy
2025-06-12 7:37 ` Bryan O'Donoghue
2025-06-12 1:15 ` [PATCH 03/10] media: qcom: camss: csiphy: simplify arguments of lanes_enable and lanes_disable Vladimir Zapolskiy
2025-06-12 8:02 ` Bryan O'Donoghue
2025-06-12 1:15 ` [PATCH 04/10] media: qcom: camss: populate CAMSS children subdevices of CSIPHY IPs Vladimir Zapolskiy
2025-06-12 1:15 ` [PATCH 05/10] media: qcom: camss: unwrap platform driver registration Vladimir Zapolskiy
2025-06-12 1:15 ` [PATCH 06/10] media: qcom: camss: export camss_parse_endpoint_node() to csiphy Vladimir Zapolskiy
2025-06-12 1:15 ` [PATCH 07/10] media: qcom: camss: csiphy: probe any present children CSIPHY subdevices Vladimir Zapolskiy
2025-06-12 1:15 ` [PATCH 08/10] dt-bindings: media: qcom: Add Qualcomm MIPI C-/D-PHY schema for CSIPHY IPs Vladimir Zapolskiy
2025-06-12 7:25 ` Krzysztof Kozlowski
2025-06-12 7:38 ` Krzysztof Kozlowski
2025-06-12 7:39 ` Krzysztof Kozlowski
2025-06-12 7:57 ` Vladimir Zapolskiy
2025-06-12 11:02 ` Krzysztof Kozlowski
2025-06-12 11:27 ` Vladimir Zapolskiy
2025-06-12 11:36 ` Krzysztof Kozlowski
2025-06-12 16:17 ` Konrad Dybcio
2025-06-12 16:44 ` Vladimir Zapolskiy
2025-06-14 19:29 ` Konrad Dybcio
2025-06-12 17:13 ` Vladimir Zapolskiy
2025-06-13 6:28 ` Krzysztof Kozlowski
2025-06-14 19:31 ` Konrad Dybcio
2025-06-17 6:32 ` Krzysztof Kozlowski
2025-06-17 9:51 ` Vladimir Zapolskiy
2025-06-17 19:20 ` Konrad Dybcio
2025-06-17 21:30 ` Vladimir Zapolskiy
2025-08-11 10:53 ` Dmitry Baryshkov
2025-06-12 1:15 ` [PATCH 09/10] [RFT] arm64: dts: qcom: sm8250: extend CAMSS with new CSIPHY subdevices Vladimir Zapolskiy
2025-06-12 7:43 ` Krzysztof Kozlowski
2025-06-12 16:25 ` Konrad Dybcio
2025-06-12 17:03 ` Vladimir Zapolskiy
2025-06-23 9:31 ` Neil Armstrong [this message]
2025-06-23 13:06 ` Vladimir Zapolskiy
2025-08-07 12:37 ` Bryan O'Donoghue
2025-08-07 14:17 ` Neil Armstrong
2025-08-07 15:07 ` Bryan O'Donoghue
2025-08-09 9:26 ` Dmitry Baryshkov
2025-08-09 11:51 ` Bryan O'Donoghue
2025-06-12 1:15 ` [PATCH 10/10] [RFT] arm64: dts: qcom: qrb5165-rb5-vision-mezzanine: switch to new CSIPHY scheme Vladimir Zapolskiy
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=bed8c29c-1365-4005-aac7-1635a28295bf@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vkoul@kernel.org \
--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).