From: Roger Quadros <rogerq@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: "stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"vigneshr@ti.com" <vigneshr@ti.com>, "srk@ti.com" <srk@ti.com>,
"r-gunasekaran@ti.com" <r-gunasekaran@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 2/2] usb: dwc3: Support 'snps,gadget-keep-connect-sys-sleep' feature
Date: Thu, 13 Apr 2023 14:31:45 +0300 [thread overview]
Message-ID: <fdfe707e-7689-373a-3aa4-e81cfeac1562@kernel.org> (raw)
In-Reply-To: <20230412205927.win6wgv6yc4nqrzt@synopsys.com>
On 12/04/2023 23:59, Thinh Nguyen wrote:
> 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.
No, this SoC can only support up to USB2 speed.
>
> Also, when you tested this in highspeed, did you observe successful
> resume? Or did the host have to perform a port reset?
I definitely didn't see a disconnect. Not sure about port reset.
I will check and get back.
cheers,
-roger
prev parent reply other threads:[~2023-04-13 11:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:34 [RFC PATCH 0/2] usb: dwc3: Support wake-up from USB suspend Roger Quadros
2023-03-20 9:34 ` [RFC PATCH 1/2] dt-bindings: usb: snps,dwc3: Add 'snps,gadget-keep-connect-sys-sleep' Roger Quadros
2023-03-20 13:11 ` Rob Herring
2023-03-20 13:22 ` Rob Herring
2023-03-21 9:44 ` Roger Quadros
2023-03-20 9:34 ` [RFC PATCH 2/2] usb: dwc3: Support 'snps,gadget-keep-connect-sys-sleep' feature Roger Quadros
2023-03-20 18:52 ` Thinh Nguyen
2023-03-21 10:20 ` Roger Quadros
2023-03-21 18:43 ` Thinh Nguyen
2023-03-21 19:05 ` Thinh Nguyen
2023-03-22 8:11 ` Roger Quadros
2023-03-22 17:31 ` Thinh Nguyen
2023-03-23 2:17 ` Thinh Nguyen
2023-03-23 9:29 ` Roger Quadros
2023-03-23 20:51 ` Thinh Nguyen
2023-03-31 11:05 ` Roger Quadros
2023-04-03 23:37 ` Thinh Nguyen
2023-04-04 8:01 ` Roger Quadros
2023-04-04 21:53 ` Thinh Nguyen
2023-04-05 8:56 ` Roger Quadros
2023-04-06 1:38 ` Thinh Nguyen
2023-04-12 7:46 ` Roger Quadros
2023-04-12 20:59 ` Thinh Nguyen
2023-04-13 11:31 ` Roger Quadros [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=fdfe707e-7689-373a-3aa4-e81cfeac1562@kernel.org \
--to=rogerq@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=r-gunasekaran@ti.com \
--cc=srk@ti.com \
--cc=stern@rowland.harvard.edu \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).