Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261454AbVBRSTX (ORCPT ); Fri, 18 Feb 2005 13:19:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261426AbVBRSTX (ORCPT ); Fri, 18 Feb 2005 13:19:23 -0500 Received: from rproxy.gmail.com ([64.233.170.195]:48944 "EHLO rproxy.gmail.com") by vger.kernel.org with ESMTP id S261454AbVBRSTN (ORCPT ); Fri, 18 Feb 2005 13:19:13 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=I92+hbfW/mp9YNTqHLdosR3l9yuL7UlRgjs7V/vuOrEv8U5+6o7wByo6q6FhmL/u7ywP2P1rAdEggu6N2+R/SVD4LuPgEg6tmaLaOFDOc6u5xrjtDMGjsq7459ov3qhjytdI7Q+/sVZlrAiif3TMUshYL7PlA0kmqYLovkGWjjU= Message-ID: Date: Fri, 18 Feb 2005 13:19:08 -0500 From: Dmitry Torokhov Reply-To: dtor_core@ameritech.net To: Vojtech Pavlik Subject: Re: 2.6: drivers/input/power.c is never built Cc: Pavel Machek , Oliver Neukum , Richard Purdie , James Simmons , Adrian Bunk , Linux Input Devices , Linux Kernel Mailing List In-Reply-To: <20050218170036.GA1672@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050213004729.GA3256@stusta.de> <047401c515bb$437b5130$0f01a8c0@max> <20050218132651.GA1813@elf.ucw.cz> <200502181436.01943.oliver@neukum.org> <20050218160153.GC12434@elf.ucw.cz> <20050218170036.GA1672@ucw.cz> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1292 Lines: 29 On Fri, 18 Feb 2005 18:00:36 +0100, Vojtech Pavlik wrote: > On Fri, Feb 18, 2005 at 05:01:53PM +0100, Pavel Machek wrote: > > > > > It has quite a lot of #ifdefs for CONFIG_APM/CONFIG_ARM/CONFIG_ACPI, > > > > and it will not work on i386/APM, anyway. I still believe right > > > > solution is to add input interface to ACPI. /proc/acpi/events needs to > > > > die, being replaced by input subsystem. > > > > > > But aren't there power events (battery low, etc) which are not > > > input events? > > > > Yes, there are. They can probably stay... Or we can get "battery low" > > key. > > We even have an event class for that, EV_PWR in the input subsystem. I really really think this is wrong. Power management should be possible without input layer. EV_PWR is fine for telling input devices to do something, like enter lower power mode and for sending _some_ requests to the PM system. But input layer shoudl not be used as a generic transport. I mean battery low, docking requests, etc has nothing to do with input. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/