From: Krzysztof Kozlowski <krzk@kernel.org>
To: Fabio Estevam <festevam@gmail.com>, gregkh@linuxfoundation.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] dt-bindings: usb: Document the Microchip USB2514 hub
Date: Fri, 5 Apr 2024 10:04:44 +0200 [thread overview]
Message-ID: <5741de00-11a0-4163-bfc2-a22c1995c96d@kernel.org> (raw)
In-Reply-To: <20240404164140.662361-1-festevam@gmail.com>
On 04/04/2024 18:41, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Document the Microchip USB2514, USB2412, and USB2417 USB hubs.
There is 2514b already. Why it cannot be there? Is the existing file
only for I2C interface and here you add on-board-hub approach interface?
If so, mention it briefly in commit msg (one sentence is enough).
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> .../bindings/usb/microchip,usb2514.yaml | 53 +++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/microchip,usb2514.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml b/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml
> new file mode 100644
> index 000000000000..8df7a5adfbe8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/microchip,usb2514.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microchip USB2514 Hub Controller
> +
> +maintainers:
> + - Fabio Estevam <festevam@gmail.com>
> +
> +properties:
> + compatible:
> + enum:
> + - usb424,2412
> + - usb424,2514
> + - usb424,2417
Please keep the list ordered.
> +
> + reg: true
> +
> + reset-gpios:
> + description: GPIO connected to the RESET_N pin.
> +
> + vdd-supply:
> + description: 3.3V power supply.
> +
> + clocks:
> + description: External 24MHz clock connected to the CLKIN pin.
maxItems.
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: true
No, this must be false.
This does not make really sense. You miss $ref... and when you do not
have $ref you should use additionalProperties: false. Open existing
bindings for device of the same class.
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/imx6qdl-clock.h>
> + #include <dt-bindings/gpio/gpio.h>
> +
> + usb {
> + dr_mode = "host";
Drop property, it's kind of expected/obvious and we want to limit
chances schema will complain about something unrelated to your device.
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + hub@1 {
> + compatible = "usb424,2514";
Inconsistent indentation. Use 4 spaces for example indentation.
> + reg = <1>;
> + clocks = <&clks IMX6QDL_CLK_CKO>;
> + reset-gpios = <&gpio7 12 GPIO_ACTIVE_LOW>;
> + vdd-supply = <®_3v3_hub>;
> + };
> + };
Best regards,
Krzysztof
prev parent reply other threads:[~2024-04-05 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 16:41 [PATCH] dt-bindings: usb: Document the Microchip USB2514 hub Fabio Estevam
2024-04-05 8:04 ` Krzysztof Kozlowski [this message]
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=5741de00-11a0-4163-bfc2-a22c1995c96d@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@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