From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bryan O'Donoghue <bod@kernel.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
Subject: Re: [PATCH v10 2/7] dt-bindings: media: qcom,x1e80100-camss: Add optional PHY handle definitions
Date: Tue, 17 Mar 2026 05:55:07 +0000 [thread overview]
Message-ID: <d104e54d-8276-4d1e-bb7d-9c01c45a7184@linaro.org> (raw)
In-Reply-To: <20260316-papaya-mink-of-examination-6db401@quoll>
On 16/03/2026 07:31, Krzysztof Kozlowski wrote:
>> +patternProperties:
>> + "^phy@[0-9a-f]+$":
>> + $ref: /schemas/phy/qcom,x1e80100-csi2-phy.yaml
>> + unevaluatedProperties: false
>> +
>> + "^opp-table(-.*)?$":
> Why do you expect multiple opp-tables?
>
> And where are operating-points phandle? Please look how other bindings
> do it.
>
>> + type: object
>> +
>> required:
>> - compatible
>> - reg
>> @@ -175,8 +201,6 @@ required:
>> - iommus
>> - power-domains
>> - power-domain-names
>> - - vdd-csiphy-0p8-supply
>> - - vdd-csiphy-1p2-supply
>> - ports
>>
>> additionalProperties: false
>> @@ -188,6 +212,7 @@ examples:
>> #include <dt-bindings/clock/qcom,x1e80100-camcc.h>
>> #include <dt-bindings/interconnect/qcom,icc.h>
>> #include <dt-bindings/interconnect/qcom,x1e80100-rpmh.h>
>> + #include <dt-bindings/phy/phy.h>
>> #include <dt-bindings/power/qcom-rpmpd.h>
>>
>> soc {
>> @@ -233,6 +258,10 @@ examples:
>> "vfe_lite0",
>> "vfe_lite1";
>>
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + ranges;
> Again, incomplete example. Where the the phy?
Both of these q's can be answered by adding a phys to the example, which
I will do.
---
bod
next prev parent reply other threads:[~2026-03-17 5:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 1:02 [PATCH v10 0/7] Add dt-bindings and dtsi changes for CAMSS on x1e80100 silicon Bryan O'Donoghue
2026-03-16 1:02 ` [PATCH v10 1/7] dt-bindings: media: qcom,x1e80100-camss: Add simple-mfd compatible Bryan O'Donoghue
2026-03-16 2:12 ` Vladimir Zapolskiy
2026-03-16 2:39 ` Dmitry Baryshkov
2026-03-16 9:28 ` Vladimir Zapolskiy
2026-03-16 7:29 ` Krzysztof Kozlowski
2026-03-16 12:01 ` Bryan O'Donoghue
2026-03-17 15:51 ` Krzysztof Kozlowski
2026-03-17 16:00 ` Krzysztof Kozlowski
2026-03-17 16:21 ` Bryan O'Donoghue
2026-03-17 16:29 ` Krzysztof Kozlowski
2026-03-17 17:29 ` Bryan O'Donoghue
2026-03-17 17:32 ` Krzysztof Kozlowski
2026-03-27 12:53 ` Konrad Dybcio
2026-03-16 1:02 ` [PATCH v10 2/7] dt-bindings: media: qcom,x1e80100-camss: Add optional PHY handle definitions Bryan O'Donoghue
2026-03-16 2:07 ` Vladimir Zapolskiy
2026-03-16 2:40 ` Dmitry Baryshkov
2026-03-16 2:50 ` Rob Herring (Arm)
2026-03-16 7:31 ` Krzysztof Kozlowski
2026-03-17 5:55 ` Bryan O'Donoghue [this message]
2026-03-16 1:02 ` [PATCH v10 3/7] dt-bindings: media: qcom,x1e80100-camss: Add support for combo-mode endpoints Bryan O'Donoghue
2026-03-16 1:02 ` [PATCH v10 4/7] dt-bindings: media: qcom,x1e80100-camss: Describe iommu entries Bryan O'Donoghue
2026-03-16 7:32 ` Krzysztof Kozlowski
2026-03-16 1:02 ` [PATCH v10 5/7] media: qcom: camss: Add legacy_phy flag to SoC definition structures Bryan O'Donoghue
2026-03-16 1:02 ` [PATCH v10 6/7] media: qcom: camss: Add support for PHY API devices Bryan O'Donoghue
2026-03-16 1:02 ` [PATCH v10 7/7] media: qcom: camss: Drop legacy PHY descriptions from x1e 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=d104e54d-8276-4d1e-bb7d-9c01c45a7184@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=bod@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.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