From: Quentin Schulz <quentin.schulz@cherry.de>
To: "Kever Yang" <kever.yang@rock-chips.com>,
"Quentin Schulz" <foss+uboot@0leil.net>,
"Klaus Goger" <klaus.goger@cherry.de>,
"Tom Rini" <trini@konsulko.com>, "Simon Glass" <sjg@chromium.org>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
王明成 <frank.wang@rock-chips.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH next 1/4] rockchip: ringneck-px30: disable broken USB gadget
Date: Tue, 16 Jul 2024 09:37:47 +0200 [thread overview]
Message-ID: <df29a993-7aef-4214-aca4-68b09d20bc63@cherry.de> (raw)
In-Reply-To: <bfc3d708-0a4d-41ce-a9a7-fe2f435a88e2@rock-chips.com>
Hi Kever,
On 7/16/24 4:04 AM, Kever Yang wrote:
> Hi Quentin,
>
> On 2024/6/14 19:04, Quentin Schulz wrote:
>> From: Quentin Schulz <quentin.schulz@cherry.de>
>>
>> USB gadget simply doesn't work right now on PX30. Tested on PX30 EVB and
>> PX30 Ringneck with Linux mainline and Rockchip 5.10 Linux as well as
>> U-Boot.
> Do you mean for both U-Boot and kernel, including mainline version and
> rockchip version,
> and on both PX30 EVB and Ringneck board, all SW&HW have no USB gadget
> working?
Mainline U-Boot on PX30 Ringneck -> not working
PX30 EVB and PX30 Ringneck in Rockchip 5.10 kernel when I tested about
two years or so ago -> working-ish, but very unstable on Ringneck and I
think not working at all on PX30 EVB
PX30 Ringneck (possibly PX30 EVB, I don't remember) in upstream 6.0.2
(and also next-20221216) -> not working
I don't know what you mean by SW&HW, how am I supposed to differentiate
the two?
FYI, I tried to add **some** support in upstream, it got merged and then
reverted because it broke STM platforms, c.f.
https://lore.kernel.org/linux-usb/20221206-dwc2-gadget-dual-role-v2-0-0de821615dd3@theobroma-systems.com/
and
https://lore.kernel.org/linux-usb/20230315144433.3095859-1-fabrice.gasnier@foss.st.com/
I can test stuff again and provide a bit more info if requested.
> So when you test this, does the maskrom mode works? because it sounds
> like maybe
> the HOST PC is the one have issue at the moment.
>
I can use rkdeveloptool just fine when using Rockchip blobs from rkbin,
no issue with the HW asf ar as I know.
Cheers,
Quentin
next prev parent reply other threads:[~2024-07-16 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 11:04 [PATCH next 0/4] rockchip: imply ARMV8_CRYPTO on px30 + px30-ringneck/rk3399-puma defconfig changes Quentin Schulz
2024-06-14 11:04 ` [PATCH next 1/4] rockchip: ringneck-px30: disable broken USB gadget Quentin Schulz
2024-07-16 2:04 ` Kever Yang
2024-07-16 7:37 ` Quentin Schulz [this message]
2024-06-14 11:04 ` [PATCH next 2/4] rockchip: ringneck-px30: enable FIT verification in SPL Quentin Schulz
2024-07-16 1:55 ` Kever Yang
2024-06-14 11:04 ` [PATCH next 3/4] rockchip: px30: imply ARMV8_CRYPTO Quentin Schulz
2024-07-16 1:55 ` Kever Yang
2024-06-14 11:04 ` [PATCH next 4/4] rockchip: puma-rk3399: add button support Quentin Schulz
2024-07-16 1:55 ` Kever Yang
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=df29a993-7aef-4214-aca4-68b09d20bc63@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=foss+uboot@0leil.net \
--cc=frank.wang@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=klaus.goger@cherry.de \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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