From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pin-yen Lin <treapking@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: usb: Add binding for PS5511 hub controller
Date: Mon, 31 Mar 2025 10:09:30 +0200 [thread overview]
Message-ID: <20250331-loud-micro-booby-e0fd4a@krzk-bin> (raw)
In-Reply-To: <20250328082950.1473406-1-treapking@chromium.org>
On Fri, Mar 28, 2025 at 04:28:45PM +0800, Pin-yen Lin wrote:
> +
> +title: PS5511 4+1 Port USB 3.2 Gen 1 Hub Controller
s/PS5511/Parade PS5511/
> +
> +maintainers:
> + - Pin-yen Lin <treapking@chromium.org>
> +
> +properties:
> + compatible:
> + enum:
> + - usb1da0,5511
> + - usb1da0,55a1
> +
> + reg: true
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + reset-gpios:
> + items:
> + - description: GPIO specifier for GRST# pin.
> +
> + vddd11-supply:
> + description:
> + 1V1 power supply to the hub
> +
> + vdd33-supply:
> + description:
> + 3V3 power supply to the hub
> +
> + peer-hub:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the peer hub on the controller.
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
I don't understand why do you need OF graph here. Children are already
defined in patternProperties as usb-devices.
Where is any upstream DTS using this schema?
> +
> + properties:
> + port@1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + 1st downstream facing USB port
> +
> + port@2:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + 2nd downstream facing USB port
> +
> + port@3:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + 3rd downstream facing USB port
> +
> + port@4:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + 4th downstream facing USB port
> +
> + port@5:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + 5th downstream facing USB port
> +
> +required:
> + - compatible
> + - reg
> + - peer-hub
> +
> +patternProperties:
patternProperties follow immediately properties, so move it up.
> + '^.*@[1-5]$':
> + description: The hard wired USB devices
> + type: object
> + $ref: /schemas/usb/usb-device.yaml
> + additionalProperties: true
> +
> +additionalProperties: false
> +
> +allOf:
> + - $ref: usb-device.yaml#
> + - if:
> + not:
> + properties:
> + compatible:
> + enum:
> + - usb1da0,usb55a1
> + then:
> + properties:
> + port@5: false
No such property.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-31 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 8:28 [PATCH 1/2] dt-bindings: usb: Add binding for PS5511 hub controller Pin-yen Lin
2025-03-28 8:28 ` [PATCH 2/2] usb: misc: onboard_usb_dev: Add Parade PS5511 hub support Pin-yen Lin
2025-03-31 8:09 ` Krzysztof Kozlowski [this message]
2025-04-08 4:30 ` [PATCH 1/2] dt-bindings: usb: Add binding for PS5511 hub controller Pin-yen Lin
2025-04-09 6:06 ` 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=20250331-loud-micro-booby-e0fd4a@krzk-bin \
--to=krzk@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=robh@kernel.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