mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] usb: dwc3: gadget: lower informal user notifaction dequeue operation
Date: Fri, 24 Mar 2023 09:30:50 +0100	[thread overview]
Message-ID: <20230324083050.GA19113@pengutronix.de> (raw)
In-Reply-To: <20230323173016.4089191-1-m.felsch@pengutronix.de>

On Thu, Mar 23, 2023 at 06:30:16PM +0100, Marco Felsch wrote:
> I encounted the below error message on the i.MX8MP if a fastboot gadget
> was up and running and barebox does a reset() or boots the kernel:
> 
>   ERROR: dwc3 38100000.usb@38100000.of: request 00000000bfd91568 was not queued to ep1out
> 
> Printing an error message during usb_ep_dequeue() is more confusing than
> helpful since the usb_ep_dequeue() could be called during unbind() like
> it is done for fastboot. Lower the dev_err() message to dev_dbg() to
> keep the message for developers.

I saw this message as well, but I deliberately kept it in. Motivated by
this patch I had a look after it. The correct solution is to not dequeue
requests in fastboot_unbind(). fastboot_disable() will already be called
which calls usb_ep_disable() which will dequeue all outstanding
requests.

See the patch I just sent.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-03-24  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 17:30 Marco Felsch
2023-03-24  8:30 ` Sascha Hauer [this message]
2023-03-24  8:39   ` Marco Felsch

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=20230324083050.GA19113@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@pengutronix.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