mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: "Frédéric Mahé" <frederic.mahe@cirad.fr>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,  Yixun Lan <dlan@kernel.org>,
	linux-riscv@lists.infradead.org,  spacemit@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: defconfig: enable onboard USB hub support
Date: Tue, 10 Nov 2026 18:13:52 -0700 (MST)	[thread overview]
Message-ID: <857db758-8aeb-178f-6acc-b163ba636863@kernel.org> (raw)
In-Reply-To: <20261109175555.323067-1-frederic.mahe@cirad.fr>

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

On Mon, 9 Nov 2026, Frédéric Mahé wrote:

> The Banana Pi BPI-F3 (SpacemiT K1) has a VL817 USB 3.0 hub behind its
> DWC3 controller. The hub's power and reset come from the
> "usb2109,2817" and "usb2109,817" nodes in the device tree, which need
> the onboard_usb_dev driver. Without it, the hub regulator (USB30_HUB)
> stays off and the board's four USB-A ports are dead.
> 
> Enable USB_ONBOARD_DEV as a module, as arm64 defconfig does.
> 
> Tested on a Banana Pi BPI-F3 with v7.4-rc1 (dwc3 enabled as a module):
> the module autoloads, the hub comes up on both buses and a USB mouse
> on a USB-A port works. Without it, only the root hubs are seen.
> 
> This patch was prepared with the help of an AI assistant (Claude),
> which also ran the build and boot tests.
> 
> Signed-off-by: Frédéric Mahé <frederic.mahe@cirad.fr>

Thanks, queued for v7.4-rc.


- Paul

      reply	other threads:[~2026-11-11  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 17:55 Frédéric Mahé
2026-11-11  1:13 ` Paul Walmsley [this message]

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=857db758-8aeb-178f-6acc-b163ba636863@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=dlan@kernel.org \
    --cc=frederic.mahe@cirad.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=spacemit@lists.linux.dev \
    /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®