From: Jung Daehwan <dh10.jung@samsung.com>
To: Wesley Cheng <wcheng@codeaurora.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Daehwan Jung <dh10.jung@samsung.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"open list:DESIGNWARE USB3 DRD IP DRIVER"
<linux-usb@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: usb: dwc3: gadget: skip pullup and set_speed after suspend
Date: Fri, 22 Jan 2021 16:15:40 +0900 [thread overview]
Message-ID: <20210122071540.GB121941@ubuntu> (raw)
In-Reply-To: <20210122064125.GA121941@ubuntu>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Fri, Jan 22, 2021 03:32, Wesley cheng wrote:
> Hi Daehwan,
>
> If this is an unexpected event where userspace initiates the UDC bind
> sequence, then after the above sequence occurs, the DWC3 device should
> still be able to re-enter runtime suspend after the autosuspend timer
> expires. Since the cable is disconnected, the dwc->connected flag would
> still be false. Is this not happening in your situation?
>
> I'm just trying to understand what issue you're seeing other than the
> momentary transition from runtime suspend (due to cable disconnect)
> -->runtime resume (due to unexpected UDC bind) --> runtime suspend (due
> to nothing connected).
>
> Thanks
> Wesley cheng
Hi Wesley,
I don't know why but DWC3 device is not re-entering runtime-suspend in
my situation. I'm still debugging it.
Even if DWC3 re-enter runtime-suspend but it doesn't mean stopping gadget.
Are you stopping gadget manually in this case?
Best Regards,
Jung Daehwan
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next parent reply other threads:[~2021-01-22 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210122065248epcas2p19a972d3a385b91d6e05a16f2ef7b0dd6@epcas2p1.samsung.com>
[not found] ` <20210122064125.GA121941@ubuntu>
2021-01-22 7:15 ` Jung Daehwan [this message]
2021-01-27 3:34 ` usb: dwc3: gadget: skip pullup and set_speed after suspend Wesley Cheng
[not found] <CGME20210120035123epcas2p2048f6d9896bd21f19d939a56fe0b6610@epcas2p2.samsung.com>
2021-01-20 3:39 ` Daehwan Jung
2021-01-21 1:00 ` Thinh Nguyen
2021-01-21 6:49 ` Jung Daehwan
2021-01-21 7:44 ` Wesley Cheng
2021-01-21 8:13 ` Jung Daehwan
2021-01-22 3:32 ` Wesley Cheng
2021-01-21 7:11 ` Jung Daehwan
2021-01-24 15:31 ` Felipe Balbi
[not found] ` <20210201054539.GA188887@ubuntu>
2021-02-01 6:06 ` Jung Daehwan
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=20210122071540.GB121941@ubuntu \
--to=dh10.jung@samsung.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wcheng@codeaurora.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;
as well as URLs for NNTP newsgroup(s).