From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [RFC] [PATCH] Make ACPI button driver an input device Date: Thu, 20 Apr 2006 16:38:48 +0100 Message-ID: <20060420153848.GA29726@srcf.ucam.org> References: <554C5F4C5BA7384EB2B412FD46A3BAD1332980@pdsmsx411.ccr.corp.intel.com> <20060420073713.GA25735@srcf.ucam.org> <4447AA59.8010300@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([217.147.92.49]:19947 "EHLO vavatch.codon.org.uk") by vger.kernel.org with ESMTP id S1751038AbWDTPiy (ORCPT ); Thu, 20 Apr 2006 11:38:54 -0400 Content-Disposition: inline In-Reply-To: <4447AA59.8010300@linux.intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alexey Starikovskiy Cc: "Yu, Luming" , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org On Thu, Apr 20, 2006 at 07:35:53PM +0400, Alexey Starikovskiy wrote: > Could it be more sensible to use kevent and dbus for sending all events > from ACPI? For most of the events, probably. I'm less convinced by the button driver - sleep and power buttons can also generate keycodes rather than ACPI events, and so getting the button driver to behave like an input device adds consistency. -- Matthew Garrett | mjg59@srcf.ucam.org