From: Rob Herring <robh@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: gregkh@linuxfoundation.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, conor+dt@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
peter.chen@kernel.org, jun.li@nxp.com, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 05/10] dt-bindings: usb: ci-hdrc-usb2-imx: add restrictions for reg, interrupts, clock and clock-names properties
Date: Tue, 12 Mar 2024 08:50:35 -0600 [thread overview]
Message-ID: <20240312145035.GA2204647-robh@kernel.org> (raw)
In-Reply-To: <20240312091703.1220649-5-xu.yang_2@nxp.com>
On Tue, Mar 12, 2024 at 05:16:58PM +0800, Xu Yang wrote:
> Add restrictions for reg, interrupts, clock and clock-names properties
> for imx Socs.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
>
> ---
> Changes in v4:
> - new patch since v3's discussion
> - split the reg, interrupts, clock and clock-names properties into
> common part and device-specific
> Changes in v5:
> - keep common property unchanged
> - make if-then more readable
> - remove non imx part
> Changes in v6:
> - new patch based on ci-hdrc-usb2-imx.yaml
> Changes in v7:
> - no changes
> Changes in v8:
> - remove if:else:if:else:if:else block
> ---
> .../bindings/usb/chipidea,usb2-imx.yaml | 80 +++++++++++++++++++
> 1 file changed, 80 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/chipidea,usb2-imx.yaml b/Documentation/devicetree/bindings/usb/chipidea,usb2-imx.yaml
> index cdbb224e9f68..fb1c378dfe88 100644
> --- a/Documentation/devicetree/bindings/usb/chipidea,usb2-imx.yaml
> +++ b/Documentation/devicetree/bindings/usb/chipidea,usb2-imx.yaml
> @@ -49,6 +49,12 @@ properties:
> - const: fsl,imx6ul-usb
> - const: fsl,imx27-usb
>
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> clocks:
> minItems: 1
> maxItems: 3
> @@ -144,6 +150,80 @@ allOf:
> - const: idle
> - const: active
>
> + # imx27 Soc needs three clocks
> + - if:
> + properties:
> + compatible:
> + const: fsl,imx27-usb
> + then:
> + properties:
> + clocks:
> + minItems: 3
> + maxItems: 3
The max is already 3, so drop maxItems.
> + clock-names:
> + items:
> + - const: ipg
> + - const: ahb
> + - const: per
> +
> + # imx25 and imx35 Soc need three clocks
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,imx25-usb
> + - fsl,imx35-usb
> + then:
> + properties:
> + clocks:
> + minItems: 3
> + maxItems: 3
Same here.
> + clock-names:
> + items:
> + - const: ipg
> + - const: ahb
> + - const: per
> +
> + # imx7d Soc need one clock
> + - if:
> + properties:
> + compatible:
> + items:
> + - const: fsl,imx7d-usb
> + - const: fsl,imx27-usb
> + then:
> + properties:
> + clocks:
> + maxItems: 1
> + clock-names:
> + maxItems: 1
What's the name?
> +
> + # other Soc need one clock
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,imx23-usb
> + - fsl,imx28-usb
> + - fsl,imx50-usb
> + - fsl,imx51-usb
> + - fsl,imx53-usb
> + - fsl,imx6q-usb
> + - fsl,imx6sl-usb
> + - fsl,imx6sx-usb
> + - fsl,imx6ul-usb
> + - fsl,imx8mm-usb
> + - fsl,imx8mn-usb
> + - fsl,vf610-usb
> + then:
> + properties:
> + clocks:
> + maxItems: 1
> + clock-names:
> + maxItems: 1
> +
> unevaluatedProperties: false
>
> examples:
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-03-12 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 9:16 [PATCH v8 01/10] dt-bindings: usb: usbmisc-imx: add fsl,imx8ulp-usbmisc compatible Xu Yang
2024-03-12 9:16 ` [PATCH v8 02/10] arm64: dts: imx8ulp: add usb nodes Xu Yang
2024-03-12 9:16 ` [PATCH v8 03/10] arm64: dts: imx8ulp-evk: enable usb nodes and add ptn5150 nodes Xu Yang
2024-03-12 9:16 ` [PATCH v8 04/10] dt-bindings: usb: chipidea,usb2-imx: move imx parts to dedicated schema Xu Yang
2024-03-12 14:51 ` Rob Herring
2024-03-12 9:16 ` [PATCH v8 05/10] dt-bindings: usb: ci-hdrc-usb2-imx: add restrictions for reg, interrupts, clock and clock-names properties Xu Yang
2024-03-12 14:50 ` Rob Herring [this message]
2024-03-13 2:48 ` [EXT] " Xu Yang
2024-03-13 3:07 ` Frank Li
2024-03-13 3:26 ` Xu Yang
2024-03-13 7:25 ` Krzysztof Kozlowski
2024-03-13 10:31 ` Xu Yang
2024-03-12 9:16 ` [PATCH v8 06/10] dt-bindings: usb: ci-hdrc-usb2-imx: add compatible and clock-names restriction for imx93 Xu Yang
2024-03-12 14:52 ` Rob Herring
2024-03-12 9:17 ` [PATCH v8 07/10] ARM: dts: imx6: remove fsl,anatop property from usb controller node Xu Yang
2024-03-12 9:17 ` [PATCH v8 08/10] arm64: dts: imx93: add usb nodes Xu Yang
2024-03-12 9:17 ` [PATCH v8 09/10] arm64: dts: imx93-11x11-evk: enable usb and typec nodes Xu Yang
2024-03-12 9:17 ` [PATCH v8 10/10] usb: chipidea: ci_hdrc_imx: align usb wakeup clock name with dt-bindings Xu Yang
2024-03-12 14:33 ` [PATCH v8 01/10] dt-bindings: usb: usbmisc-imx: add fsl,imx8ulp-usbmisc compatible Rob Herring
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=20240312145035.GA2204647-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).