Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Prashanth K <quic_prashk@quicinc.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Fix latency of DSTS while receiving wakeup event
Date: Wed, 14 Aug 2024 09:52:02 +0530	[thread overview]
Message-ID: <04fc6990-b249-29cb-bc15-7fe85292f6a0@quicinc.com> (raw)
In-Reply-To: <20240813233043.uhsxocjr2pn4ujle@synopsys.com>



On 14-08-24 05:00 am, Thinh Nguyen wrote:
>>> When we receive the wakeup event, then the device is no longer in
>>> L1/L2/U3. The Start Tranfer command should go through. >
>> Ok will do this, I hope there won't be any corner cases where the link is
>> down when start_xfer happens. I was not really sure about the history, thats
>> why tried to incorporate my fix into the above IF check.
>>
> 
> It was initially implemented verbatim base on the Start Transfer command
> suggestion from the programming guide without considering the dwc3
> driver flow. First dwc3 checks for U1/U2/U3 state. Then we fixed to only
> check for L1/L2/U3 state, but it's still not right. I've had this on my
> TODO list for awhile and haven't made an update since it's not critical.
> 
Sure, thanks for the confirmation, will send v2.

Regards,
Prashanth K

      reply	other threads:[~2024-08-14  4:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 12:47 [PATCH] usb: dwc3: Fix latency of DSTS while receiving wakeup event Prashanth K
2024-08-06 23:51 ` Thinh Nguyen
2024-08-07  9:41   ` Prashanth K
2024-08-08  0:06     ` Thinh Nguyen
2024-08-13  9:53       ` Prashanth K
2024-08-13 23:30         ` Thinh Nguyen
2024-08-14  4:22           ` Prashanth K [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=04fc6990-b249-29cb-bc15-7fe85292f6a0@quicinc.com \
    --to=quic_prashk@quicinc.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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