From: Rosen Penev <rosenp@gmail.com>
To: devicetree@vger.kernel.org
Cc: "Florian Fainelli" <florian.fainelli@broadcom.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM5301X ARM ARCHITECTURE),
linux-kernel@vger.kernel.org (open list),
linux-usb@vger.kernel.org (open list:USB SUBSYSTEM)
Subject: [PATCH 0/2] usb: bcma: control VBUS via a regulator
Date: Sun, 20 Sep 2026 14:13:54 -0700 [thread overview]
Message-ID: <20260920211356.186967-1-rosenp@gmail.com> (raw)
bcma-hcd currently drives the USB power line by grabbing the
undocumented "vcc-gpio" property from the controller node and poking
it through gpiolib. Besides relying on a non-standard binding, this
cannot work on boards such as the NETGEAR R7000 and R8000 where one
chipcommon GPIO powers both the USB2 and USB3 cores: the two
controllers each request that GPIO exclusively, so the second one
fails with -EBUSY and its port stays dead.
Instead, switch the driver to the standard regulator interface and
express the power rails as regulator-fixed nodes bound to the
chipcommon GPIOs. The regulator core reference-counts enable/disable
requests, letting both controllers share one GPIO without conflicts.
Rosen Penev (2):
usb: bcma: control VBUS via a regulator instead of a GPIO
ARM: dts: broadcom: model USB VBUS power with regulator-fixed
.../broadcom/bcm4708-buffalo-wxr-1750dhp.dts | 14 +++++-
.../bcm4708-buffalo-wzr-1166dhp-common.dtsi | 25 ++++++++++-
.../broadcom/bcm4708-buffalo-wzr-1750dhp.dts | 25 ++++++++++-
.../broadcom/bcm4708-linksys-ea6300-v1.dts | 14 +++++-
.../broadcom/bcm4708-linksys-ea6500-v2.dts | 14 +++++-
.../dts/broadcom/bcm4708-netgear-r6250.dts | 14 +++++-
.../dts/broadcom/bcm4708-netgear-r6300-v2.dts | 14 +++++-
.../dts/broadcom/bcm47081-luxul-xwr-1200.dts | 14 +++++-
.../broadcom/bcm47081-tplink-archer-c5-v2.dts | 14 +++++-
.../dts/broadcom/bcm4709-asus-rt-ac3200.dts | 14 +++++-
.../broadcom/bcm4709-buffalo-wxr-1900dhp.dts | 14 +++++-
.../dts/broadcom/bcm4709-linksys-ea9200.dts | 26 ++++++++++-
.../dts/broadcom/bcm4709-netgear-r7000.dts | 16 ++++++-
.../dts/broadcom/bcm4709-netgear-r8000.dts | 16 ++++++-
.../broadcom/bcm4709-tplink-archer-c9-v1.dts | 26 ++++++++++-
.../dts/broadcom/bcm47094-asus-rt-ac3100.dtsi | 14 +++++-
.../dts/broadcom/bcm47094-asus-rt-ac5300.dts | 14 +++++-
.../dts/broadcom/bcm47094-dlink-dir-885l.dts | 14 +++++-
.../dts/broadcom/bcm47094-dlink-dir-890l.dts | 26 ++++++++++-
.../broadcom/bcm47094-linksys-panamera.dts | 26 ++++++++++-
.../dts/broadcom/bcm47094-luxul-abr-4500.dts | 14 +++++-
.../dts/broadcom/bcm47094-luxul-xbr-4500.dts | 14 +++++-
.../dts/broadcom/bcm47094-luxul-xwr-3100.dts | 14 +++++-
.../broadcom/bcm47094-luxul-xwr-3150-v1.dts | 14 +++++-
.../arm/boot/dts/broadcom/bcm947189acdbmr.dts | 14 +++++-
drivers/usb/host/bcma-hcd.c | 45 +++++++++++++------
26 files changed, 422 insertions(+), 47 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-20 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 21:13 Rosen Penev [this message]
2026-09-20 21:13 ` [PATCH 1/2] usb: bcma: control VBUS via a regulator instead of a GPIO Rosen Penev
2026-09-20 21:13 ` [PATCH 2/2] ARM: dts: broadcom: model USB VBUS power with regulator-fixed Rosen Penev
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=20260920211356.186967-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zajec5@gmail.com \
/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®