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] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 12 Apr 2023 20:59:31 +0000
From:   Thinh Nguyen <Thinh.Nguyen@...opsys.com>
To:     Roger Quadros <rogerq@...nel.org>
CC:     Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
        "stern@...land.harvard.edu" <stern@...land.harvard.edu>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "vigneshr@...com" <vigneshr@...com>, "srk@...com" <srk@...com>,
        "r-gunasekaran@...com" <r-gunasekaran@...com>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 2/2] usb: dwc3: Support
 'snps,gadget-keep-connect-sys-sleep' feature

On Wed, Apr 12, 2023, Roger Quadros wrote:
> 
> 
> On 06/04/2023 04:38, Thinh Nguyen wrote:
> > On Wed, Apr 05, 2023, Roger Quadros wrote:
> >>
> >>
> >> On 05/04/2023 00:53, Thinh Nguyen wrote:
> >>>
> >>> I may have misunderstood your platform implementation. My understanding
> >>> is that it can only detect VBUS and that it can only resume on VBUS
> >>> valid.
> >>>
> >>> Does the "LINESTATE" here gets asserted if say there's a LFPS detection?
> >>
> >> Yes. The wake up logic on the SoC is snooping the UTMI lines from the PHY and on any
> >> change it can detect and wake up the SoC.
> >>
> > 
> > Are you referring to the utmi_linestate signal? Isn't that for usb2
> > speed only? Does your platform support usb3 speed?
> 
> The wake-up on deepSleep feature is only supported for USB2 on this particular SoC.
> 

I mean can your platform operate in usb3 speed. If that's the case, then
how do you plan to handle it here.

Also, when you tested this in highspeed, did you observe successful
resume? Or did the host have to perform a port reset?

Thanks,
Thinh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ