From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: Wakeup settings for USB hubs? Date: Thu, 5 Jul 2007 21:18:59 +0200 Message-ID: <200707052118.59885.oliver@neukum.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org Am Donnerstag, 5. Juli 2007 schrieb Alan Stern: > Allow me to rephrase. =A0You seem to be saying that /sys/.../power/wake= up=20 > should be able to hold four different values: >=20 > =A0=A0=A0=A0=A0=A0=A0=A01. always disabled > =A0=A0=A0=A0=A0=A0=A0=A02. always enabled > =A0=A0=A0=A0=A0=A0=A0=A03. enabled at runtime but not during system sle= ep > =A0=A0=A0=A0=A0=A0=A0=A04. enabled during system sleep but not at runti= me >=20 > Right? =A0With the default being 3 (except for a few things like the=20 > power button). >=20 > Or maybe there should be two attribute files: wakeup (used during > system sleep) and wakeup_runtime (used for runtime suspend). >=20 > Comments from anybody else? I am not sure we ever want to do runtime suspend without remote wakeup. If we want that then it is orthogonal to its value during system sleep. That would call for two attributes. Regards Oliver