From: Angelo Dureghello <angelo@kernel-space.org>
To: Alan Stern <stern@rowland.harvard.edu>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: testusb: epipe errors on test 9 and 10
Date: Fri, 28 Nov 2025 22:21:05 +0100 [thread overview]
Message-ID: <4430e4b6-9556-4c93-8b63-4c7abc79307d@kernel-space.org> (raw)
In-Reply-To: <bcc4f76a-985b-4932-a455-b4fedcafcd97@rowland.harvard.edu>
Hi Alan,
On 11/28/25 17:10, Alan Stern wrote:
> On Fri, Nov 28, 2025 at 10:20:25AM -0500, Alan Stern wrote:
>> On Fri, Nov 28, 2025 at 03:20:35PM +0100, Angelo Dureghello wrote:
>>> Hi Alan,
>>>
>>> thanks a lot,
>>>
>>> On 11/28/25 04:23, Alan Stern wrote:
>>>> I think this is the expected behavior; g_zero does not support
>>>> Get-Interface-Status.
>>> ok, good to know. Btw, on this article seems all tests are passing
>>>
>>> https://bootlin.com/blog/test-a-linux-kernel-usb-device-controller-driver-with-testusb/
>>>
>>> but not really clear what what "test must pass" is.
>> It looks like something may have changed between the time when that
>> article was written and now. I would expect g-zero to support
>> Get-Interface-Status, since it is a standard request.
> This was wrong; I had forgotten that Get-Status requests are mostly
> handled by the UDC driver, not by the gadget drivers. In your case, I
> guess that's dwc3?
>
> In the current kernel, these requests are handled in
> drivers/usb/dwc3/ep0.c:dwc3_ep0_handle_status(). The problem is that
> this routine doesn't handle Get-Interface-Status requests at all;
> instead it passes them through to the composite core, which doesn't
> handle many of them either. Other UDC drivers do a better job.
>
> Fixing this should be pretty easy, but I'm not not an expert on dwc3.
> The maintainer, Thinh Nguyen, will know what to do.
Thanks a lot, really, will look this direction so.
> Alan Stern
angelo
next prev parent reply other threads:[~2025-11-28 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 8:06 testusb: epipe errors on test 9 and 10 Angelo Dureghello
2025-11-27 8:22 ` Greg KH
2025-11-27 12:53 ` Angelo Dureghello
2025-11-27 13:21 ` Greg KH
2025-11-28 3:23 ` Alan Stern
2025-11-28 14:20 ` Angelo Dureghello
2025-11-28 15:20 ` Alan Stern
2025-11-28 16:10 ` Alan Stern
2025-11-28 21:21 ` Angelo Dureghello [this message]
2025-12-01 23:29 ` Thinh Nguyen
2025-12-02 3:09 ` Alan Stern
2025-12-02 4:23 ` Thinh Nguyen
2025-12-02 16:25 ` Alan Stern
2025-12-02 23:22 ` Thinh Nguyen
2025-12-04 22:26 ` Alan Stern
2025-12-10 14:20 ` Angelo Dureghello
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=4430e4b6-9556-4c93-8b63-4c7abc79307d@kernel-space.org \
--to=angelo@kernel-space.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.