From: Neil Armstrong <neil.armstrong@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: phy: qcom,sc8280xp-qmp-usb43dp: do not reference whole usb-switch.yaml
Date: Wed, 17 Sep 2025 09:00:36 +0200 [thread overview]
Message-ID: <6d5009cf-9332-4c0f-acf3-baa6a0be3f0d@linaro.org> (raw)
In-Reply-To: <56ddc607-f30b-410b-af54-e2d9afc06540@linaro.org>
Hi,
On 08/09/2025 09:33, Neil Armstrong wrote:
> On 05/09/2025 19:55, Rob Herring wrote:
>> On Tue, Sep 02, 2025 at 06:10:05PM +0200, Neil Armstrong wrote:
>>> Both bindings describe a different layout of the ports properties,
>>> leading to errors when validating DT using this PHY bindings as
>>> reported by Rob Herring.
>>>
>>> Reported-by: Rob Herring <robh@kernel.org>
>>> Closes: https://lore.kernel.org/all/175462129176.394940.16810637795278334342.robh@kernel.org/
>>> Fixes: 3bad7fe22796 ("dt-bindings: phy: qcom,sc8280xp-qmp-usb43dp: Reference usb-switch.yaml to allow mode-switch")
>>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>>> ---
>>> .../devicetree/bindings/phy/qcom,sc8280xp-qmp-usb43dp-phy.yaml | 8 +++++---
>>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb43dp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb43dp-phy.yaml
>>> index c8bc512df08b5694c8599f475de78679a4438449..5005514d7c3a1e4a8893883497fd204bc04e12be 100644
>>> --- a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb43dp-phy.yaml
>>> +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb43dp-phy.yaml
>>> @@ -73,8 +73,11 @@ properties:
>>> description:
>>> See include/dt-bindings/phy/phy-qcom-qmp.h
>>> - mode-switch: true
>>> - orientation-switch: true
>>> + mode-switch:
>>> + $ref: /schemas/usb/usb-switch.yaml#properties/mode-switch
>>> +
>>> + orientation-switch:
>>> + $ref: /schemas/usb/usb-switch.yaml#properties/orientation-switch
>>
>> This is a pattern we try to avoid with references at a property level. I
>> prefer you make port and ports not required in usb-switch.yaml.
>
> Sure but the ports definitions will still collide in this case.
>
> The other problem here is the difference in ports definition,
> port@0 and port@1 are not the same.
>
> qcom,sc8280xp-qmp-usb43dp-phy.yaml:
> ports:
> $ref: /schemas/graph.yaml#/properties/ports
> properties:
> port@0:
> $ref: /schemas/graph.yaml#/properties/port
> description: Output endpoint of the PHY
>
> port@1:
> $ref: /schemas/graph.yaml#/properties/port
> description: Incoming endpoint from the USB controller
>
> port@2:
> $ref: /schemas/graph.yaml#/properties/port
> description: Incoming endpoint from the DisplayPort controller
>
> usb-switch.yaml:
> ports:
> $ref: /schemas/graph.yaml#/properties/ports
> properties:
> port@0:
> $ref: /schemas/graph.yaml#/properties/port
> description:
> Super Speed (SS) Output endpoint to the Type-C connector
>
> port@1:
> $ref: /schemas/graph.yaml#/$defs/port-base
> description:
> Super Speed (SS) Input endpoint from the Super-Speed PHY
Do you have any advice how to solve this ? Requires is not the problem, the problem is to have the port
definitions in usb-switch.yaml
Neil
>
> Neil
>
>>
>> Rob
>
next prev parent reply other threads:[~2025-09-17 7:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 16:10 Neil Armstrong
2025-09-03 8:01 ` Krzysztof Kozlowski
2025-09-05 17:55 ` Rob Herring
2025-09-08 7:33 ` Neil Armstrong
2025-09-17 7:00 ` Neil Armstrong [this message]
2025-09-30 19:10 ` Dmitry Baryshkov
2025-10-01 7:07 ` Neil Armstrong
2025-10-01 16:31 ` Rob Herring
2025-10-02 7:26 ` Neil Armstrong
2025-10-06 8:41 ` Neil Armstrong
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=6d5009cf-9332-4c0f-acf3-baa6a0be3f0d@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®