From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: simon@fire.lp0.eu, jonas.gorski@gmail.com, kishon@ti.com,
vkoul@kernel.org, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com, p.zabel@pengutronix.de,
krzk@kernel.org, gregkh@linuxfoundation.org, alcooperx@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/2] dt-bindings: phy: add bcm63xx-usbh bindings
Date: Thu, 9 Jul 2020 16:11:05 -0600 [thread overview]
Message-ID: <20200709221105.GA976808@bogus> (raw)
In-Reply-To: <20200619100035.4032596-2-noltari@gmail.com>
On Fri, Jun 19, 2020 at 12:00:34PM +0200, Álvaro Fernández Rojas wrote:
> Document BCM63xx USBH PHY bindings.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> v5: no changes.
> v4: conditionally require 1/2 clocks and fix clock/reset values.
> v3: no changes.
> v2: phy-cells changed to 1.
>
> .../bindings/phy/brcm,bcm63xx-usbh-phy.yaml | 84 +++++++++++++++++++
> 1 file changed, 84 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml
>
> diff --git a/Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml b/Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml
> new file mode 100644
> index 000000000000..f267da6193a9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml
> @@ -0,0 +1,84 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/phy/brcm,bcm63xx-usbh-phy.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: BCM63xx USBH PHY
> +
> +maintainers:
> + - Álvaro Fernández Rojas <noltari@gmail.com>
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,bcm6318-usbh-phy
> + - brcm,bcm6328-usbh-phy
> + - brcm,bcm6358-usbh-phy
> + - brcm,bcm6362-usbh-phy
> + - brcm,bcm6368-usbh-phy
> + - brcm,bcm63268-usbh-phy
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + const: usbh
> +
> + resets:
> + maxItems: 1
> +
> + "#phy-cells":
> + const: 1
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - resets
> + - "#phy-cells"
You need:
additionalProperties: false
> +
> +allOf:
> + - if:
> + properties:
> + compatible:
> + enum:
> + - brcm,bcm6318-usbh-phy
> + - brcm,bcm63268-usbh-phy
> + then:
> + properties:
> + clocks:
> + maxItems: 2
This doesn't work. The main schema will also be applied and it says
there's 1. The main schema has to cover all the cases and then if/then
schemas add constraints.
> + clock-names:
> + items:
> + - const: usbh
> + - const: usb_ref
> + - if:
> + properties:
> + compatible:
> + enum:
> + - brcm,bcm6318-usbh-phy
> + - brcm,bcm6328-usbh-phy
> + - brcm,bcm6362-usbh-phy
> + - brcm,bcm63268-usbh-phy
> + then:
> + properties:
> + power-domains:
> + maxItems: 1
> + required:
> + - power-domains
> +
> +examples:
> + - |
> + usbh: usb-phy@10001700 {
> + compatible = "brcm,bcm6368-usbh-phy";
> + reg = <0x10001700 0x38>;
> + clocks = <&periph_clk 15>;
> + clock-names = "usbh";
> + resets = <&periph_rst 12>;
> + #phy-cells = <1>;
> + };
> --
> 2.27.0
>
next prev parent reply other threads:[~2020-07-09 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 10:00 [PATCH v5 0/2] phy: bcm63xx-usbh: Add BCM63xx USBH driver Álvaro Fernández Rojas
2020-06-19 10:00 ` [PATCH v5 1/2] dt-bindings: phy: add bcm63xx-usbh bindings Álvaro Fernández Rojas
2020-07-09 22:11 ` Rob Herring [this message]
2020-07-13 13:55 ` Álvaro Fernández Rojas
2020-06-19 10:00 ` [PATCH v5 2/2] phy: bcm63xx-usbh: Add BCM63xx USBH driver Álvaro Fernández Rojas
2020-06-20 4:01 ` Florian Fainelli
2020-07-13 5:51 ` Vinod Koul
2020-07-13 13:59 ` Álvaro Fernández Rojas
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=20200709221105.GA976808@bogus \
--to=robh@kernel.org \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonas.gorski@gmail.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=simon@fire.lp0.eu \
--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