From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure Date: Wed, 25 Nov 2009 21:21:55 -0800 Message-ID: <20091126052155.GD23244@core.coreip.homeip.net> References: <200910200956.33391.jarod@redhat.com> <200910200958.50574.jarod@redhat.com> <4B0A765F.7010204@redhat.com> <4B0A81BF.4090203@redhat.com> <20091123173726.GE17813@core.coreip.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pw0-f42.google.com ([209.85.160.42]:38762 "EHLO mail-pw0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750850AbZKZFVy (ORCPT ); Thu, 26 Nov 2009 00:21:54 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Krzysztof Halasa Cc: Mauro Carvalho Chehab , Jarod Wilson , linux-kernel@vger.kernel.org, Mario Limonciello , linux-input@vger.kernel.org, linux-media@vger.kernel.org, Janne Grunau , Christoph Bartelmus On Mon, Nov 23, 2009 at 09:51:31PM +0100, Krzysztof Halasa wrote: > Dmitry Torokhov writes: > > > Curreently the "scan" codes in the input layer serve just to help users > > to map whatever the device emits into a proper input event code so that > > the rest of userspace would not have to care and would work with all > > types of devices (USB, PS/2, etc). > > > > I would not want to get to the point where the raw codes are used as a > > primary data source. > > The "key" interface is not flexible enough at present. > In what way the key interface is unsufficient for delivering button events? -- Dmitry