linux-kernel - Re: [PATCH v3 3/3] usb: phy: hold wakeupsource when USB is enumerated in peripheral mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Nov 2014 08:45:44 -0600
From:	Felipe Balbi <balbi@...com>
To:	Peter Chen <Peter.Chen@...escale.com>
CC:	Kiran Raparthy <kiran.kumar@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Felipe Balbi <balbi@...com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	Android Kernel Team <kernel-team@...roid.com>,
	John Stultz <john.stultz@...aro.org>,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Arve Hjønnevåg <arve@...roid.com>,
	Benoit Goby <benoit@...roid.com>,
	Todd Poynor <toddpoynor@...gle.com>
Subject: Re: [PATCH v3 3/3] usb: phy: hold wakeupsource when USB is
 enumerated in peripheral mode

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

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)