From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@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>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] dt-bindings: phy: Add Qualcomm MIPI C-/D-PHY schema for CSIPHY IPs
Date: Wed, 14 May 2025 22:30:26 +0300 [thread overview]
Message-ID: <634e9d0d-fbab-4101-b968-d335b656e099@linaro.org> (raw)
In-Reply-To: <959b9c65-50d7-426d-9c2a-64e143e28ded@kernel.org>
Hello Krzysztof.
On 5/14/25 13:25, Krzysztof Kozlowski wrote:
> On 13/05/2025 16:39, Vladimir Zapolskiy wrote:
>> Add dt-binding schema for the CAMSS CSIPHY IPs, which provides
>> MIPI C-/D-PHY interfaces on Qualcomm SoCs.
>>
>> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
>> ---
>> .../devicetree/bindings/phy/qcom,csiphy.yaml | 110 ++++++++++++++++++
>> 1 file changed, 110 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/phy/qcom,csiphy.yaml
>
>
> Looks like not tested, so limited review follows.
>
> Filename matching compatible.
>
Thank you for the review, the change is deliberately tagged as RFC.
I read this review comment as the displayed generic compatible 'qcom,csiphy'
shall be added to the list of compatibles.
>>
>> diff --git a/Documentation/devicetree/bindings/phy/qcom,csiphy.yaml b/Documentation/devicetree/bindings/phy/qcom,csiphy.yaml
>> new file mode 100644
>> index 000000000000..ef712c5442ec
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/qcom,csiphy.yaml
>
> Please post the driver or any other user. Or explain why this is RFC or
> what you expect here from us.
>
The CSIPHY driver agnostic CAMSS changes are on the linux-media list [1], the CSIPHY
driver specific changes will be added on top of these changes, however I believe
it makes sense to review these two different CAMSS changesets independently.
Here the RFC tag is given explicitly to get change reviews for the dt binding
documentation part, and the first user is the example embedded into the change.
>> @@ -0,0 +1,110 @@
>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/phy/qcom,csiphy.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Qualcomm CSI PHY
>
> SM8250 ?
>
It's supposed to be a generic device tree binding, and it covers SM8250
CAMSS CSIPHY IP as well, which could be quite handly for testing/review.
>> +
>> +maintainers:
>> + - Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
>> +
>> +description: |
>
> Do not need '|' unless you need to preserve formatting.
>
Ack.
>> + Qualcomm SoCs equipped with a number of MIPI CSI PHY IPs, which
>> + supports D-PHY or C-PHY interfaces to camera sensors.
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - qcom,sm8250-csiphy
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + clocks:
>> + maxItems: 2
>
> Need to list the items instead
>
Ack.
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + vdda-csi-0p9-supply:
>> + description: Voltage supply, 0.9V
>> +
>> + vdda-csi-1p2-supply:
>> + description: Voltage supply, 1.2V
>> +
>> + '#phy-cells':
>> + const: 0
>> +
>> + port:
>> + $ref: /schemas/graph.yaml#/$defs/port-base
>> + description: CAMSS CSIPHY input port
>> +
>> + patternProperties:
>> + "^endpoint@[0-1]$":
>
> Keep consistent quotes, either " or '
>
Ack.
>> + $ref: /schemas/media/video-interfaces.yaml#
>> + unevaluatedProperties: false
>> +
>> + properties:
>> + data-lanes:
>> + minItems: 1
>> + maxItems: 4
>> +
>> + bus-type:
>> + enum:
>> + - 1 # MEDIA_BUS_TYPE_CSI2_CPHY
>> + - 4 # MEDIA_BUS_TYPE_CSI2_DPHY
>> +
>> + required:
>> + - data-lanes
>> +
>> + oneOf:
>> + - required:
>> + - endpoint
>> + - required:
>> + - endpoint@0
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - clocks
>> + - interrupts
>> + - '#phy-cells'
>> +
>> +allOf:
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - qcom,sm8250-csiphy
>> + then:
>> + required:
>> + - vdda-csi-0p9-supply
>> + - vdda-csi-1p2-supply
>
> This makes no sense - it is only sm8250 - so this if is always true.
>
Ack, thank you for the review comments.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2025-05-14 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 14:39 [RFC PATCH] dt-bindings: phy: Add Qualcomm MIPI C-/D-PHY schema for CSIPHY IPs Vladimir Zapolskiy
2025-05-13 14:48 ` Conor Dooley
2025-05-13 15:31 ` Rob Herring (Arm)
2025-05-14 0:59 ` Dmitry Baryshkov
2025-05-14 8:17 ` Vinod Koul
2025-05-14 10:25 ` Krzysztof Kozlowski
2025-05-14 19:30 ` Vladimir Zapolskiy [this message]
2025-05-15 9:16 ` Krzysztof Kozlowski
2025-05-14 10:29 ` 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=634e9d0d-fbab-4101-b968-d335b656e099@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vkoul@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