From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Xu Yang <xu.yang_2@nxp.com>,
vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, gregkh@linuxfoundation.org, jun.li@nxp.com,
l.stach@pengutronix.de, aford173@gmail.com, hongxing.zhu@nxp.com,
alexander.stein@ew.tq-group.com, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: phy: imx8mq-usb: add compatible "fsl,imx95-usb-phy"
Date: Wed, 7 Aug 2024 07:48:43 +0200 [thread overview]
Message-ID: <bfe6430c-a022-4e8f-ab7f-8d8e8cb10fca@kernel.org> (raw)
In-Reply-To: <ZrJLS37GFmvkQpml@lizhi-Precision-Tower-5810>
On 06/08/2024 18:11, Frank Li wrote:
> On Tue, Aug 06, 2024 at 10:29:47AM +0200, Krzysztof Kozlowski wrote:
>> On 06/08/2024 07:06, Xu Yang wrote:
>>> The usb phy in i.MX95 is compatible with i.MX8MP's, this will add a
>>> compatible "fsl,imx95-usb-phy" for i.MX95. Also change reg maxItems
>>> to 2 since i.MX95 needs another regmap to control Type-C Assist (TCA)
>>> block. Since i.MX95 usb phy is able to switch SS lanes, this will also
>>> add orientation-switch and port property to the file.
>>>
>>> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
>>>
>>> ---
>>> Changes in v2:
>>> - replace minItems with description in reg property
>>> - remove orientation-switch and port
>>> - refer to usb-switch.yaml
>>> - use unevaluatedProperties
>>> ---
>>> .../bindings/phy/fsl,imx8mq-usb-phy.yaml | 42 ++++++++++++++++---
>>> 1 file changed, 37 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml
>>> index dc3a3f709fea..6d6d211883ae 100644
>>> --- a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml
>>> +++ b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml
>>> @@ -11,12 +11,17 @@ maintainers:
>>>
>>> properties:
>>> compatible:
>>> - enum:
>>> - - fsl,imx8mq-usb-phy
>>> - - fsl,imx8mp-usb-phy
>>> + oneOf:
>>> + - enum:
>>> + - fsl,imx8mq-usb-phy
>>> + - fsl,imx8mp-usb-phy
>>> + - items:
>>> + - const: fsl,imx95-usb-phy
>>> + - const: fsl,imx8mp-usb-phy
>>>
>>> reg:
>>> - maxItems: 1
>>> + minItems: 1
>>> + maxItems: 2
>>>
>>> "#phy-cells":
>>> const: 0
>>> @@ -89,7 +94,34 @@ required:
>>> - clocks
>>> - clock-names
>>>
>>> -additionalProperties: false
>>> +allOf:
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - fsl,imx95-usb-phy
>>> + then:
>>> + properties:
>>> + reg:
>>> + items:
>>> + - description: USB PHY Control range
>>> + - description: USB PHY TCA Block range
>>> + else:
>>> + properties:
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - fsl,imx95-usb-phy
>>> + then:
>>> + $ref: /schemas/usb/usb-switch.yaml#
>>
>> ref should be rather in top-level. You can always disallow certain
>> properties for devices, if they are really not applicable.
>
> There are some "required" in usb-switch.yaml,
>
> oneOf:
> - required:
> - port
> - required:
> - ports
>
> If put on the top, it may cause DTB check warning for other compatible
> strings, which have not support usb-switch.
Hm, indeed, that's unusual case to have such different devices in one
schema. Did you test that above $ref in if: actually works?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-07 5:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 5:06 [PATCH v2 1/5] dt-bindings: phy: imx8mq-usb: add compatible "fsl,imx95-usb-phy" Xu Yang
2024-08-06 5:06 ` [PATCH v2 2/5] dt-bindings: usb: dwc3-imx8mp: add compatible string for imx95 Xu Yang
2024-08-06 5:06 ` [PATCH v2 3/5] phy: fsl-imx8mq-usb: add tca function driver " Xu Yang
2024-08-06 5:06 ` [PATCH v2 4/5] arm64: dts: imx95: add usb3 related nodes Xu Yang
2024-08-06 5:06 ` [PATCH v2 5/5] arm64: dts: imx95-19x19-evk: add typec nodes and enable usb3 node Xu Yang
2024-08-06 8:29 ` [PATCH v2 1/5] dt-bindings: phy: imx8mq-usb: add compatible "fsl,imx95-usb-phy" Krzysztof Kozlowski
2024-08-06 16:11 ` Frank Li
2024-08-07 2:24 ` Xu Yang
2024-08-07 5:48 ` Krzysztof Kozlowski [this message]
2024-08-07 5:57 ` Xu Yang
2024-08-07 5:59 ` Krzysztof Kozlowski
2024-08-07 7:11 ` Xu Yang
2024-08-07 7:20 ` Krzysztof Kozlowski
2024-08-07 7:20 ` Krzysztof Kozlowski
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=bfe6430c-a022-4e8f-ab7f-8d8e8cb10fca@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.li@nxp.com \
--cc=aford173@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@kernel.org \
--cc=xu.yang_2@nxp.com \
/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).