From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Minas Harutyunyan <hminas@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [Query]usb: dwc2: suspend/resume support for DWC2_POWER_DOWN_PARAM_NONE case
Date: Tue, 16 Jun 2020 17:03:11 +0800 [thread overview]
Message-ID: <20200616164712.67bf105c@xhacker.debian> (raw)
Hi,
After reading current dwc2 code, I got an impression that resume from suspend
to ram isn't supported for DWC2_POWER_DOWN_PARAM_NONE case, right? In fact
we do see usb device can't resume properly with DWC2_POWER_DOWN_PARAM_NONE case.
If the impression is true, what's the proper technical direction? Add
dwc2_host_enter_suspend() as dwc2_host_enter_hibernation()
and
dwc2_host_exit_suspend() as dwc2_host_exit_hibernation()?
Thanks in advance,
Jisheng
next reply other threads:[~2020-06-16 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 9:03 Jisheng Zhang [this message]
2020-06-16 13:53 ` [Query]usb: dwc2: suspend/resume support for DWC2_POWER_DOWN_PARAM_NONE case Minas Harutyunyan
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=20200616164712.67bf105c@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).