From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Halasa 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: Mon, 23 Nov 2009 21:51:31 +0100 Message-ID: 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: In-Reply-To: <20091123173726.GE17813@core.coreip.homeip.net> (Dmitry Torokhov's message of "Mon, 23 Nov 2009 09:37:27 -0800") Sender: linux-media-owner@vger.kernel.org To: Dmitry Torokhov 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 List-Id: linux-input@vger.kernel.org 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. > Again, I would prefer to keep EV_KEY/KEY_* as the primary event type for > keys and buttons on all devices. Primary, I think so. -- Krzysztof Halasa