linux-kernel - Re: [PATCH] usb: dwc3: Fix latency of DSTS while receiving wakeup event

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <04fc6990-b249-29cb-bc15-7fe85292f6a0@quicinc.com>
Date: Wed, 14 Aug 2024 09:52:02 +0530
From: Prashanth K <quic_prashk@...cinc.com>
To: Thinh Nguyen <Thinh.Nguyen@...opsys.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Fix latency of DSTS while receiving wakeup
 event



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