From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: 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>,
Neil Armstrong <neil.armstrong@linaro.org>,
Bryan O'Donoghue <bod@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v17 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema
Date: Thu, 10 Sep 2026 09:21:56 +0200 [thread overview]
Message-ID: <20260910-enlightened-charming-antelope-a812da@quoll> (raw)
In-Reply-To: <20260903-x1e-csi2-phy-v17-1-26606fa9a039@linaro.org>
On Thu, Sep 03, 2026 at 09:44:33PM +0100, Bryan O'Donoghue wrote:
> + clock-lanes:
> + maxItems: 1
> +
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> + items:
> + minimum: 1
> + maximum: 4
> + description:
> + Data lane positions following this endpoint's clock
> + lane. Positions are a per-port logical numbering, not
> + package pad or ball positions.
> +
> + required:
> + - data-lanes
> + - remote-endpoint
> +
> + allOf:
> + - if:
> + required:
> + - endpoint@1
> + then:
> + properties:
> + endpoint@0:
> + properties:
> + clock-lanes:
> + const: 0
> + data-lanes:
> + maxItems: 2
> + endpoint@1:
> + properties:
> + clock-lanes:
> + const: 3
> + data-lanes:
> + items:
> + - const: 4
> + required:
> + - endpoint@0
> + else:
> + patternProperties:
> + "^endpoint(@0)?$":
> + properties:
> + clock-lanes:
> + const: 0
So endpoint@0 has a fixed clock-lanes? Then the property is redundant
and you can completely drop it.
> +
> + port@1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Output to the CAMSS CSID controller.
> +
> + required:
> + - port@0
> + - port@1
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: 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>,
Neil Armstrong <neil.armstrong@linaro.org>,
Bryan O'Donoghue <bod@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v17 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema
Date: Thu, 10 Sep 2026 09:21:56 +0200 [thread overview]
Message-ID: <20260910-enlightened-charming-antelope-a812da@quoll> (raw)
In-Reply-To: <20260903-x1e-csi2-phy-v17-1-26606fa9a039@linaro.org>
On Thu, Sep 03, 2026 at 09:44:33PM +0100, Bryan O'Donoghue wrote:
> + clock-lanes:
> + maxItems: 1
> +
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> + items:
> + minimum: 1
> + maximum: 4
> + description:
> + Data lane positions following this endpoint's clock
> + lane. Positions are a per-port logical numbering, not
> + package pad or ball positions.
> +
> + required:
> + - data-lanes
> + - remote-endpoint
> +
> + allOf:
> + - if:
> + required:
> + - endpoint@1
> + then:
> + properties:
> + endpoint@0:
> + properties:
> + clock-lanes:
> + const: 0
> + data-lanes:
> + maxItems: 2
> + endpoint@1:
> + properties:
> + clock-lanes:
> + const: 3
> + data-lanes:
> + items:
> + - const: 4
> + required:
> + - endpoint@0
> + else:
> + patternProperties:
> + "^endpoint(@0)?$":
> + properties:
> + clock-lanes:
> + const: 0
So endpoint@0 has a fixed clock-lanes? Then the property is redundant
and you can completely drop it.
> +
> + port@1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Output to the CAMSS CSID controller.
> +
> + required:
> + - port@0
> + - port@1
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-10 7:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 20:44 [PATCH v17 0/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-09-03 20:44 ` Bryan O'Donoghue
2026-09-03 20:44 ` [PATCH v17 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema Bryan O'Donoghue
2026-09-03 20:44 ` Bryan O'Donoghue
2026-09-03 20:59 ` sashiko-bot
2026-09-03 20:59 ` sashiko-bot
2026-09-09 14:18 ` Loic Poulain
2026-09-09 14:18 ` Loic Poulain
2026-09-10 7:21 ` Krzysztof Kozlowski [this message]
2026-09-10 7:21 ` Krzysztof Kozlowski
2026-09-03 20:44 ` [PATCH v17 2/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-09-03 20:44 ` Bryan O'Donoghue
2026-09-03 20:54 ` sashiko-bot
2026-09-03 20:54 ` sashiko-bot
2026-09-06 15:51 ` [PATCH v17 0/2] " Nihal Kumar Gupta
2026-09-06 15:51 ` Nihal Kumar Gupta
2026-09-16 10:17 ` Krzysztof Kozlowski
2026-09-16 10:17 ` Krzysztof Kozlowski
2026-09-16 11:29 ` Nihal Kumar Gupta
2026-09-16 11:29 ` Nihal Kumar Gupta
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=20260910-enlightened-charming-antelope-a812da@quoll \
--to=krzk@kernel.org \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.