linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"Kever Yang" <kever.yang@rock-chips.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hervé Codina" <herve.codina@bootlin.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Stefan Wahren" <wahrenst@gmx.net>,
	"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>
Subject: Re: DWC2 gadget: unexpected device reenumeration on Rockchip RK3308
Date: Tue, 15 Apr 2025 17:58:22 +0200	[thread overview]
Message-ID: <20250415175822.1c537ae9@booty> (raw)
In-Reply-To: <20250415162825.083f351c@booty>

Hello again,

On Tue, 15 Apr 2025 16:28:25 +0200
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:

[...]

> There are two more facts that may hint at something:
> 
>  * using the Rockchip 4.4 vendor kernel the problem does never happen
>  * using a custom board with the RK3308 the problem happens if the
>    USB-C cable is connected before booting; it does not happen if the
>    connectror is connected after the boot has completed
> 
> These two have been reported to me and I haven't reproduced them (yet)
> so I cannot provide logs at the moment. I can prioritize working on
> them, or the 4.4 vendor kernel at least, if it is deemed useful.

FWIW I managed to try the 4.4 vendor kernel:

git repo: https://github.com/radxa/kernel.git
commit:   4.4.143-23-rockchip-796-g09ee299143e4

As said, there is only one enumerations, not two.

Here's a log of the host during said enumeration (same host as before,
no changes on the host side):

[110685.837058] hub 3-3:1.0: state 7 ports 4 chg 0000 evt 0010
[110685.844824] usb 3-3-port4: status 0101, change 0001, 12 Mb/s
[110685.848278] usb 3-3-port4: indicator auto status 0
[110685.958750] usb 3-3-port4: debounce total 100ms stable 100ms status 0x101
[110686.053638] usb 3-3.4: new high-speed USB device number 116 using xhci_hcd
[110686.163756] usb 3-3.4: skipped 2 descriptors after configuration
[110686.163775] usb 3-3.4: skipped 4 descriptors after interface
[110686.163996] usb 3-3.4: default language 0x0409
[110686.164557] usb 3-3.4: udev 116, busnum 3, minor = 371
[110686.164567] usb 3-3.4: New USB device found, idVendor=1209, idProduct=0001, bcdDevice= 1.00
[110686.164574] usb 3-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[110686.164579] usb 3-3.4: Product: foobar
[110686.164583] usb 3-3.4: Manufacturer: ACME
[110686.164586] usb 3-3.4: SerialNumber: 12345678
[110686.165279] usb 3-3.4: usb_probe_device
[110686.165290] usb 3-3.4: configuration #1 chosen from 1 choice
[110686.169116] usb 3-3.4: adding 3-3.4:1.0 (config #1, interface 0)
[110686.169384] cdc_acm 3-3.4:1.0: usb_probe_interface
[110686.169389] cdc_acm 3-3.4:1.0: usb_probe_interface - got id
[110686.169827] cdc_acm 3-3.4:1.0: ttyACM0: USB ACM device
[110686.169868] usb 3-3.4: adding 3-3.4:1.1 (config #1, interface 1)

The only potentially significant difference I could spot from the
previous host log is:

mainline:  [105021.396995] usb 3-3.4: skipped 1 descriptor after configuration
 4.4:      [110686.163756] usb 3-3.4: skipped 2 descriptors after configuration

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2025-04-15 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 16:54 DWC2 gadget: unexpected device reenumeration on Rockchip RK3308 Luca Ceresoli
2025-04-14 17:26 ` Alan Stern
2025-04-15 11:26   ` Minas Harutyunyan
2025-04-15 14:28     ` Luca Ceresoli
2025-04-15 15:58       ` Luca Ceresoli [this message]
2025-04-15 16:14       ` Alan Stern
2025-05-02 13:53         ` Luca Ceresoli
2025-05-02 17:56           ` Alan Stern
2025-05-09  7:17             ` Luca Ceresoli
2025-05-13  7:35               ` Minas Harutyunyan
2025-05-20 12:09                 ` Luca Ceresoli
2025-06-12 13:23                   ` Louis Chauvet

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=20250415175822.1c537ae9@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=Minas.Harutyunyan@synopsys.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herve.codina@bootlin.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wahrenst@gmx.net \
    /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;
as well as URLs for NNTP newsgroup(s).