From: Rob Herring <robh@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Matthias Kaehlcke <mka@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v4 3/5] dt-bindings: usb: usb-device: add usb hub port vbus-supply suppport
Date: Mon, 15 Sep 2025 15:58:49 -0500 [thread overview]
Message-ID: <20250915205849.GA3379566-robh@kernel.org> (raw)
In-Reply-To: <20250911-v6-16-topic-usb-onboard-dev-v4-3-1af288125d74@pengutronix.de>
On Thu, Sep 11, 2025 at 10:22:44PM +0200, Marco Felsch wrote:
> Some PCB designs don't use the dedicated USB hub port power control GPIO
> to control the port VBUS supply. Instead host managed GPIOs are used to
> control the VBUS supply.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> Documentation/devicetree/bindings/usb/usb-device.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/usb-device.yaml b/Documentation/devicetree/bindings/usb/usb-device.yaml
> index 09fceb469f10525e9dcdb91435b142b0d21964b8..2f891a05ab9bca095eb881c5f601ac27ac63b542 100644
> --- a/Documentation/devicetree/bindings/usb/usb-device.yaml
> +++ b/Documentation/devicetree/bindings/usb/usb-device.yaml
> @@ -53,6 +53,12 @@ properties:
> "#size-cells":
> const: 0
>
> + vbus-supply:
> + description: USB hub port VBUS supply.
> + The host managed regulator which controlls the USB hub port VBUS. This
controls
With that,
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> + regulator is only required if the hub internal control signals aren't
> + used to control the VBUS regulators.
> +
> patternProperties:
> "^interface@[0-9a-f]{1,2}(,[0-9a-f]{1,2})$":
> type: object
>
> --
> 2.47.3
>
next prev parent reply other threads:[~2025-09-15 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 20:22 [PATCH v4 0/5] Add onboard-dev USB hub host managed vbus handling support Marco Felsch
2025-09-11 20:22 ` [PATCH v4 1/5] usb: port: track the disabled state Marco Felsch
2025-09-11 20:22 ` [PATCH v4 2/5] usb: hub: add infrastructure to pass onboard_dev port features Marco Felsch
2025-09-11 20:22 ` [PATCH v4 3/5] dt-bindings: usb: usb-device: add usb hub port vbus-supply suppport Marco Felsch
2025-09-15 20:58 ` Rob Herring [this message]
2025-09-11 20:22 ` [PATCH v4 4/5] dt-bindings: usb: microchip,usb2514: add vbus-supply example Marco Felsch
2025-09-12 0:17 ` Rob Herring (Arm)
2025-09-12 8:51 ` Marco Felsch
2025-09-12 14:11 ` Rob Herring
2025-09-12 15:30 ` Marco Felsch
2025-09-11 20:22 ` [PATCH v4 5/5] usb: misc: onboard_dev: add hub downstream port host vbus-supply handling Marco Felsch
2026-02-10 6:23 ` [PATCH v4 0/5] Add onboard-dev USB hub host managed vbus handling support Ze Huang
2026-02-10 12:32 ` Marco Felsch
2026-02-10 13:20 ` Greg Kroah-Hartman
2026-02-23 11:29 ` Marco Felsch
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=20250915205849.GA3379566-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=mka@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