From: Quentin Schulz <quentin.schulz@cherry.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: trini@konsulko.com, sjg@chromium.org, kever.yang@rock-chips.com,
u-boot@lists.u-boot-project.org,
Fabio Estevam <festevam@nabladev.com>
Subject: Re: [PATCH v3] rockchip: rk3588s: Add support for ROC-PC-RK3588S
Date: Thu, 23 Jul 2026 14:23:46 +0200 [thread overview]
Message-ID: <bdaf952e-41ef-4ad7-95fa-93443d6552ae@cherry.de> (raw)
In-Reply-To: <CAOMZO5AGM3Lm5=rfECDnkgwokTOxb=T9ww3+gqS9wdXpm-bQ+w@mail.gmail.com>
Hi Fabio,
On 7/23/26 1:31 PM, Fabio Estevam wrote:
> Hi Quentin,
>
> On Thu, Jul 23, 2026 at 7:01 AM Quentin Schulz <quentin.schulz@cherry.de> wrote:
>
>> Just to be sure this isn't an oversight, DWC3 is used for
>> usb_host0_xhci, which is enabled on ROC-PC-RK3588S. I see there are a
>> USB-A port marked as USB3 on the product datasheet, and also USB OTG
>> that is capable of doing USB3. I couldn't quickly find schematics to
>> verify what's what, so does the full USB-A marked as being USB3 capable
>> still working?
>
> Personally, I am not using any of the two USB host ports in U-Boot.
>
> USB host support in U-Boot can be added later if someone needs it.
>
Fair enough.
>> It's actually ROC-RK3588S-PC (c.f.
>> https://wiki.t-firefly.com/en/ROC-RK3588S-PC/), I can fix this up when
>> applying if you want, if there's no need for a v4 based on feedback above.
>
> Please fix this up while applying.
>
Thanks!
Quentin
prev parent reply other threads:[~2026-07-23 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 18:40 [PATCH v3] rockchip: rk3588s: Add support for ROC-PC-RK3588S Fabio Estevam via U-Boot
2026-07-23 10:01 ` Quentin Schulz
2026-07-23 11:31 ` Fabio Estevam
2026-07-23 12:23 ` Quentin Schulz [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=bdaf952e-41ef-4ad7-95fa-93443d6552ae@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=kever.yang@rock-chips.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox