From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Li Haifeng <omycle@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"Felipe.Balbi@microsoft.com" <Felipe.Balbi@microsoft.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Issue with DWC3 Gadget Driver: Stall After Transmitting Only 2KB Using Scatter-Gather and TRB Chaining
Date: Fri, 31 Oct 2025 22:41:20 +0000 [thread overview]
Message-ID: <20251031224113.4ml474v6fuiytkcf@synopsys.com> (raw)
In-Reply-To: <CAFNq8R6uZSS3+nWXkR8XERjMRGTC_4_47UKm_N=P8Um5ySLAtg@mail.gmail.com>
Hi,
On Thu, Oct 30, 2025, Li Haifeng wrote:
> Dear Greg,
>
> Thank you for your prompt response and advice.
>
> I just tested the issue on kernel version 6.1.17, and the problem
> persists. I will proceed to try the latest kernel release 6.17, and
> report back with the results as soon as possible.
>
> Appreciate your guidance.
>
> Best regards,
> Haifeng
>
Avoid top-post if you can.
As Greg noted, please try the recent kernel release. For now, let's take
a look at what you already have.
This is from your previous email:
- The device side only transmits the first 2KB of data.
- The host acknowledges this partial transfer (ACK received).
- After the ACK, the device does not respond or continue the
transfer—no further data is sent, and the endpoint appears to stall
without triggering any completion callback or error.
You mentioned host ACK'ed IN data, so I assume you run in SuperSpeed and
have a usb traffic analyzer and able to see these packets. Did you see
the host requesting for the next set of data? My suspiction is it did
not. There's no mention of NRDY or flow control here. If the device did
not prepare enough TRBs, you'd see flow control.
Check your host.
BR,
Thinh
next prev parent reply other threads:[~2025-10-31 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 8:49 Issue with DWC3 Gadget Driver: Stall After Transmitting Only 2KB Using Scatter-Gather and TRB Chaining Li Haifeng
2025-10-30 9:39 ` Greg KH
2025-10-30 12:47 ` Li Haifeng
2025-10-31 22:41 ` Thinh Nguyen [this message]
2025-11-03 6:22 ` Li Haifeng
2025-11-04 1:16 ` Thinh Nguyen
2025-11-04 1:20 ` Thinh Nguyen
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=20251031224113.4ml474v6fuiytkcf@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=Felipe.Balbi@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=omycle@gmail.com \
/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