From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: anis chali <chalianis1@gmail.com>, Sascha Hauer <sascha@saschahauer.de>
Subject: Re: [PATCH v2 0/3] USB: dwc2: Fix handling NAK
Date: Mon, 15 Jun 2026 13:34:49 +0200 [thread overview]
Message-ID: <178152328964.3162138.6414056430742952499.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260602-usb-dwc2-usb-c-stick-v2-0-0e02782c7e32@pengutronix.de>
On Tue, 02 Jun 2026 11:29:19 +0200, Sascha Hauer wrote:
> A NAK should return -EAGAIN to let the retry logic work. This showed up
> on a Samsung USB-C memory stick which otherwise was recognized, but
> couldn't be initialized.
>
> The v2 now adddresses Anis' log spamming problems. The solution here is
> to just silence the error message by turning it into dev_dbg. The
> message says "Timeout on bulk endpoint" which is normal and expected
> behaviour. The usbnet driver expects bulk messages to timeout when
> no RX data is available.
>
> [...]
Applied, thanks!
[1/3] usb: dwc2: Do not print error messages when URBs are nacked
https://git.pengutronix.de/cgit/barebox/commit/?id=eef830fc6158 (link may not be stable)
[2/3] usb: dwc2: handle NAK when CHHLTD does not fire
https://git.pengutronix.de/cgit/barebox/commit/?id=a7548991ea36 (link may not be stable)
[3/3] usb: dwc2: fix data toggle reset direction on ClearFeature(ENDPOINT_HALT)
https://git.pengutronix.de/cgit/barebox/commit/?id=4db628f5d0f4 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-06-15 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 9:29 Sascha Hauer
2026-06-02 9:29 ` [PATCH v2 1/3] usb: dwc2: Do not print error messages when URBs are nacked Sascha Hauer
2026-06-02 9:29 ` [PATCH v2 2/3] usb: dwc2: handle NAK when CHHLTD does not fire Sascha Hauer
2026-06-02 9:29 ` [PATCH v2 3/3] usb: dwc2: fix data toggle reset direction on ClearFeature(ENDPOINT_HALT) Sascha Hauer
2026-06-15 11:34 ` Sascha Hauer [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=178152328964.3162138.6414056430742952499.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=chalianis1@gmail.com \
--cc=sascha@saschahauer.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