From: Yixun Lan <dlan@kernel.org>
To: Marek Vasut <marek.vasut+usb@mailbox.org>,
Hung-Chun Tseng <alan.tseng.cs@gmail.com>
Cc: Tom Rini <trini@konsulko.com>, Huan Zhou <pericycle.cc@gmail.com>,
Eric Chung <eric.chung@riscstar.com>,
Alexey Charkov <alchark@flipper.net>,
Guodong Xu <docular.xu@gmail.com>,
Raymond Mao <raymond.mao@riscstar.com>,
Zixian Zeng <sycamoremoon376@gmail.com>,
u-boot-spacemit@groups.io, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v2 1/2] usb: onboard-hub: Add support for VIA Labs VL817
Date: Fri, 13 Nov 2026 06:15:28 +0000 [thread overview]
Message-ID: <20261113061528-GKA73509@kernel.org> (raw)
In-Reply-To: <20261113031613.435429-2-alan.tseng.cs@gmail.com>
Hi Marek,
On 11:16 Fri 13 Nov , Hung-Chun Tseng wrote:
> The VL817 is a USB 3.1 Gen 1 hub controller with one supply and a reset
> pin. Use the same reset time as Linux.
>
> The Milk-V Jupiter and the Banana Pi BPI-F3 have one in front of all
> their USB ports. Without this, U-Boot leaves the hub unpowered and in
> reset, so no USB device is found.
>
> Signed-off-by: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
> Tested-by: Zixian Zeng <sycamoremoon376@gmail.com> # Babanapi-F3
> ---
> common/usb_onboard_hub.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
would you prefer to take this patch via usb tree?
or I could queue it in spacemit custodian tree,
either way works for me, just let me know
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-11-13 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 3:16 [PATCH v2 0/2] usb: onboard-hub: VL817 support for SpacemiT K1 boards Hung-Chun Tseng
2026-11-13 3:16 ` [PATCH v2 1/2] usb: onboard-hub: Add support for VIA Labs VL817 Hung-Chun Tseng
2026-11-13 3:45 ` Marek Vasut
2026-11-13 6:15 ` Yixun Lan [this message]
2026-11-13 3:16 ` [PATCH v2 2/2] configs: spacemit_k1: Enable onboard USB hub support Hung-Chun Tseng
2026-11-13 6:07 ` [PATCH v2 0/2] usb: onboard-hub: VL817 support for SpacemiT K1 boards Yixun Lan
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=20261113061528-GKA73509@kernel.org \
--to=dlan@kernel.org \
--cc=alan.tseng.cs@gmail.com \
--cc=alchark@flipper.net \
--cc=docular.xu@gmail.com \
--cc=eric.chung@riscstar.com \
--cc=marek.vasut+usb@mailbox.org \
--cc=pericycle.cc@gmail.com \
--cc=raymond.mao@riscstar.com \
--cc=sycamoremoon376@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot-spacemit@groups.io \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.