public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Bin Liu <b-liu@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] usb: musb: fix MUSB_QUIRK_B_DISCONNECT_99 handling
Date: Mon, 31 May 2021 14:40:34 +0300	[thread overview]
Message-ID: <YLTLMnLlkhaJ29AO@atomide.com> (raw)
In-Reply-To: <YLENtd45ly8ZFJO2@piout.net>

* Alexandre Belloni <alexandre.belloni@bootlin.com> [210528 15:35]:
> On 28/05/2021 16:04:46+0200, Thomas Petazzoni wrote:
> > In commit 92af4fc6ec33 ("usb: musb: Fix suspend with devices
> > connected for a64"), the logic to support the
> > MUSB_QUIRK_B_DISCONNECT_99 quirk was modified to only conditionally
> > schedule the musb->irq_work delayed work.
> > 
> > This commit badly breaks ECM Gadget on AM335X. Indeed, with this
> > commit, one can observe massive packet loss:
> > 
> > $ ping 192.168.0.100
> > ...
> > 15 packets transmitted, 3 received, 80% packet loss, time 14316ms
> > 
> > Reverting this commit brings back a properly functioning ECM
> > Gadget. An analysis of the commit seems to indicate that a mistake was
> > made: the previous code was not falling through into the
> > MUSB_QUIRK_B_INVALID_VBUS_91, but now it is, unless the condition is
> > taken.
> > 
> > Changing the logic to be as it was before the problematic commit *and*
> > only conditionally scheduling musb->irq_work resolves the regression:
> > 
> > $ ping 192.168.0.100
> > ...
> > 64 packets transmitted, 64 received, 0% packet loss, time 64475ms
> > 
> > Fixes: 92af4fc6ec33 ("usb: musb: Fix suspend with devices connected for a64")
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>

Ouch, sorry about that one. And thanks for fixing it:

Acked-by: Tony Lindgren <tony@atomide.com>

  reply	other threads:[~2021-05-31 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 14:04 [PATCH] usb: musb: fix MUSB_QUIRK_B_DISCONNECT_99 handling Thomas Petazzoni
2021-05-28 15:35 ` Alexandre Belloni
2021-05-31 11:40   ` Tony Lindgren [this message]
2021-05-31 17:28 ` Drew Fustini

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=YLTLMnLlkhaJ29AO@atomide.com \
    --to=tony@atomide.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=b-liu@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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