From: Rob Herring <robh@kernel.org>
To: Pin-yen Lin <treapking@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: usb: Add binding for PS5511 hub controller
Date: Wed, 16 Apr 2025 13:00:23 -0500 [thread overview]
Message-ID: <20250416180023.GB3327258-robh@kernel.org> (raw)
In-Reply-To: <20250415094227.3629916-3-treapking@chromium.org>
On Tue, Apr 15, 2025 at 05:41:59PM +0800, Pin-yen Lin wrote:
> Parade PS5511 is USB hub with 4 USB 3.2 compliant 5Gbps downstream(DS)
> ports, and 1 extra USB 2.0 downstream port. The hub has one reset pin
> control and two power supplies (3V3 and 1V1).
>
> Signed-off-by: Pin-yen Lin <treapking@chromium.org>
>
> ---
>
> Changes in v2:
> - Inherit usb-hub.yaml
> - Fix bindings to reject port@5/device@5 for 3.0 hub correctly
> - Minor string fixes
>
> .../bindings/usb/parade,ps5511.yaml | 115 ++++++++++++++++++
> 1 file changed, 115 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/parade,ps5511.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/parade,ps5511.yaml b/Documentation/devicetree/bindings/usb/parade,ps5511.yaml
> new file mode 100644
> index 00000000000000..86c75d69ee35b2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/parade,ps5511.yaml
> @@ -0,0 +1,115 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/parade,ps5511.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Parade PS5511 4+1 Port USB 3.2 Gen 1 Hub Controller
> +
> +maintainers:
> + - Pin-yen Lin <treapking@chromium.org>
> +
> +properties:
> + compatible:
> + enum:
> + - usb1da0,5511
> + - usb1da0,55a1
> +
> + reg: true
> +
> + '#address-cells': true
> +
> + '#size-cells': true
Drop these 3.
> +
> + reset-gpios:
> + items:
> + - description: GPIO specifier for RESETB pin.
> +
> + vddd11-supply:
> + description:
> + 1V1 power supply to the hub
> +
> + vdd33-supply:
> + description:
> + 3V3 power supply to the hub
> +
> + peer-hub: true
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + '#address-cells': true
> +
> + '#size-cells': true
> +
> + patternProperties:
> + '^port@[1-5]$': true
> +
> + additionalProperties: false
I would do this instead:
ports:
$ref: /schemas/graph.yaml#/properties/ports
patternProperties:
'^port@':
$ref: /schemas/graph.yaml#/properties/port
properties:
reg:
minimum: 1
maximum: 5
> +
> +patternProperties:
> + '^.*@[1-5]$': true
And here:
additionalProperties: true
properties:
reg:
minimum: 1
maximum: 5
> +
> +required:
> + - compatible
> + - reg
Already required by usb-hub.yaml.
> + - peer-hub
> +
> +additionalProperties: false
Use unevaluatedProperties instead.
> +
> +allOf:
> + - $ref: usb-hub.yaml#
> + - if:
> + not:
> + properties:
> + compatible:
> + enum:
> + - usb1da0,55a1
> + then:
> + properties:
> + ports:
> + properties:
> + port@5: false
> + patternProperties:
> + '^.*@5$': false
> +
> +examples:
> + - |
> + usb {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + /* 2.0 hub on port 1 */
> + hub_2_0: hub@1 {
> + compatible = "usb1da0,55a1";
> + reg = <1>;
> + peer-hub = <&hub_3_0>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + /* USB 2.0 device on port 5 */
> + device@5 {
> + reg = <5>;
> + compatible = "usb123,4567";
> + };
> + };
> +
> + /* 3.0 hub on port 2 */
> + hub_3_0: hub@2 {
> + compatible = "usb1da0,5511";
> + reg = <2>;
> + peer-hub = <&hub_2_0>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + /* Type-A connector on port 3 */
> + port@3 {
> + reg = <3>;
> + endpoint {
> + remote-endpoint = <&usb_a0_ss>;
> + };
> + };
> + };
> + };
> + };
> --
> 2.49.0.777.g153de2bbd5-goog
>
next prev parent reply other threads:[~2025-04-16 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 9:41 [PATCH v2 0/4] Introduce usb-hub.yaml binding and add support for Parade PS5511 Pin-yen Lin
2025-04-15 9:41 ` [PATCH v2 1/4] dt-bindings: usb: Introduce usb-hub.yaml Pin-yen Lin
2025-04-16 16:52 ` Rob Herring
2025-04-15 9:41 ` [PATCH v2 2/4] dt-bindings: usb: Add binding for PS5511 hub controller Pin-yen Lin
2025-04-16 18:00 ` Rob Herring [this message]
2025-04-15 9:42 ` [PATCH v2 3/4] dt-bindings: usb: realtek,rts5411: Adapt usb-hub.yaml Pin-yen Lin
2025-04-16 18:01 ` Rob Herring
2025-04-15 9:42 ` [PATCH v2 4/4] usb: misc: onboard_usb_dev: Add Parade PS5511 hub support Pin-yen Lin
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=20250416180023.GB3327258-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=swboyd@chromium.org \
--cc=treapking@chromium.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;
as well as URLs for NNTP newsgroup(s).