From: Felipe Balbi <balbi@ti.com>
To: Peter Chen <Peter.Chen@freescale.com>
Cc: "Kiran Raparthy" <kiran.kumar@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Felipe Balbi" <balbi@ti.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Android Kernel Team" <kernel-team@android.com>,
"John Stultz" <john.stultz@linaro.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Benoit Goby" <benoit@android.com>,
"Todd Poynor" <toddpoynor@google.com>
Subject: Re: [PATCH v3 3/3] usb: phy: hold wakeupsource when USB is enumerated in peripheral mode
Date: Tue, 25 Nov 2014 08:45:44 -0600 [thread overview]
Message-ID: <20141125144544.GC6360@saruman> (raw)
In-Reply-To: <15cad5ef7627483cbba96e05fe180813@BN1PR0301MB0772.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Tue, Nov 25, 2014 at 07:06:18AM +0000, Peter Chen wrote:
>
> >
> > usb: phy: hold wakeupsource when USB is enumerated in peripheral mode
> >
> > Some systems require a mechanism to prevent system to enter into suspend
> > state when USB is connected and enumerated in peripheral mode.
> >
> > This patch provides an interface to hold a wakeupsource to prevent suspend.
> > PHY drivers can use this interface when USB is connected and enumerated in
> > peripheral mode.
> >
> > A timed wakeupsource is temporarily held on USB disconnect events, to allow
> > the rest of the system to react to the USB disconnection (dropping host
> > sessions, updating charger status, etc.) prior to re-allowing suspend.
> >
>
> Hi Kiran & Felipe,
>
> Just two questions for this series
>
> - Will it be the default behavior for all peripheral drivers?
> - If the peripheral driver's PHY driver does not vbus event, how to
> support it?
> For example, chipidea udc driver has its vbus interface at its
> controller register.
hmm, good point. Since it's so late, I'll just go ahead and drop
$subject from v3.20. Let's delay only $subject to v3.20 merge window so
we have some more time to discuss these details.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-25 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 17:24 [PATCH v3 1/3] usb: phy: introduce usb_phy_set_event interface Kiran Raparthy
2014-11-24 17:24 ` [PATCH v3 2/3] usb: phy: Handle per-PHY event for connect and disconnect events Kiran Raparthy
2014-11-24 17:25 ` [PATCH v3 3/3] usb: phy: hold wakeupsource when USB is enumerated in peripheral mode Kiran Raparthy
2014-11-25 7:06 ` Peter Chen
2014-11-25 14:45 ` Felipe Balbi [this message]
2014-12-01 5:39 ` Kiran Raparthy
2015-01-13 10:32 ` Kiran Raparthy
2015-01-13 16:18 ` Felipe Balbi
2015-01-14 1:26 ` Peter Chen
2015-06-08 7:07 ` Sumit Semwal
2015-06-08 8:32 ` Peter Chen
2015-07-13 7:56 ` Sumit Semwal
2015-07-13 7:00 ` Peter Chen
2015-07-20 7:48 ` Sumit Semwal
2015-07-20 7:15 ` Peter Chen
2015-07-20 13:07 ` Sumit Semwal
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=20141125144544.GC6360@saruman \
--to=balbi@ti.com \
--cc=Peter.Chen@freescale.com \
--cc=arve@android.com \
--cc=benoit@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=kiran.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=toddpoynor@google.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