From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.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 v3 3/4] dt-bindings: usb: microchip,usb2514: add support for port vbus-supply
Date: Sun, 24 Aug 2025 11:03:18 +0200 [thread overview]
Message-ID: <dc4046e5-7912-4942-b313-20f29213773c@kernel.org> (raw)
In-Reply-To: <20250822103005.c7ba7dclbgdadyw7@pengutronix.de>
On 22/08/2025 12:30, Marco Felsch wrote:
>> The binding does not list ports now, but lists hard-wired devices, so my
>> question is now: is this per hard-wired device or per port (even if port
>> is hot-pluggable)?
>
> Sorry but I don't get you. The binding lists the regulators required to
> enable/disable the hub downstream port VBUS. These regulators are
Is the port an external facing connector or a hard-wired USB device
(please read the binding)?
> controlled by an external party e.g. the CPU instead of the USB hub
> itself. The connection from the CPU to the regulator which controlls the
> +5V usb-connector pin is hard-wired, yes.
I speak about USB devices.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-24 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 16:31 [PATCH v3 0/4] Add ext. port vbus handling for onboard-dev Marco Felsch
2025-08-21 16:31 ` [PATCH v3 1/4] usb: port: track the disabled state Marco Felsch
2025-08-21 16:31 ` [PATCH v3 2/4] usb: hub: add infrastructure to pass onboard_dev port features Marco Felsch
2025-08-21 16:31 ` [PATCH v3 3/4] dt-bindings: usb: microchip,usb2514: add support for port vbus-supply Marco Felsch
2025-08-22 8:23 ` Krzysztof Kozlowski
2025-08-22 10:30 ` Marco Felsch
2025-08-22 20:05 ` Rob Herring
2025-09-03 22:57 ` Marco Felsch
2025-08-24 9:03 ` Krzysztof Kozlowski [this message]
2025-09-03 23:10 ` Marco Felsch
2025-08-21 16:31 ` [PATCH v3 4/4] usb: misc: onboard_dev: add ext-vbus-supply handling 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=dc4046e5-7912-4942-b313-20f29213773c@kernel.org \
--to=krzk@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 \
--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
all inboxes | Powered by JetHome®