From: Manu Gautam <mgautam@codeaurora.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Felipe Balbi <balbi@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
USB <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] usb: dwc3: Support the dwc3 host suspend/resume
Date: Mon, 24 Jul 2017 14:12:11 +0530 [thread overview]
Message-ID: <e6b182f8-50c0-04ae-570b-5a6369fb50dd@codeaurora.org> (raw)
In-Reply-To: <CAMz4kuJonfVvaa-gWExuEDh1s5bgipXeC3chASOx8dmmLK-HLQ@mail.gmail.com>
Hi Baolin,
On 7/24/2017 11:26 AM, Baolin Wang wrote:
>>>> Other than what I pushed in my patch -
>>>> ("usb: dwc3: Don't reinitialize core during host bus-suspend/resume")
>>>> Just performing pm_request_resume or handling same in dwc3 glue
>>>> driver should be sufficient.
>>> Yes.
>>>
>>>> Also, what is trigger for runtime_resume for your platform?
>>> In our platform glue layer, we have extcon events to notify there are
>>> devices connected, then gule layer will resume dwc3 device.
>>>
>> IMO you can just perform resume of &dwc->xhci->dev instead of resuming dwc3.
>> Since, dwc3 is parent of xhci that will trigger resume of dwc3 as well.
> I am not sure this is good enough but it seems can solve some
> problems, then we do not need resume/suspend host in dwc3 core.
In that case can we proceed with this patch:
[1] https://www.spinics.net/lists/linux-usb/msg158682.html
For your platform you can pick this patch and resume dwc->xhci->dev resume
from your glue driver.
Do you have any other concerns?
next prev parent reply other threads:[~2017-07-24 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 6:58 Baolin Wang
2017-07-21 8:45 ` Manu Gautam
2017-07-21 9:01 ` Baolin Wang
2017-07-21 9:13 ` Manu Gautam
2017-07-24 5:56 ` Baolin Wang
2017-07-24 8:42 ` Manu Gautam [this message]
2017-07-24 9:15 ` Baolin Wang
2017-07-24 9:38 ` Manu Gautam
2017-07-24 11:42 ` Baolin Wang
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=e6b182f8-50c0-04ae-570b-5a6369fb50dd@codeaurora.org \
--to=mgautam@codeaurora.org \
--cc=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linaro-kernel@lists.linaro.org \
--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
all inboxes | Powered by JetHome®