Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754584AbZLHMhu (ORCPT ); Tue, 8 Dec 2009 07:37:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754415AbZLHMht (ORCPT ); Tue, 8 Dec 2009 07:37:49 -0500 Received: from mail1.radix.net ([207.192.128.31]:55078 "EHLO mail1.radix.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754311AbZLHMhr (ORCPT ); Tue, 8 Dec 2009 07:37:47 -0500 Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure From: Andy Walls To: Dmitry Torokhov Cc: Jarod Wilson , Mauro Carvalho Chehab , Krzysztof Halasa , Christoph Bartelmus , j@jannau.net, jarod@redhat.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, superm1@ubuntu.com In-Reply-To: <20091208042210.GA11147@core.coreip.homeip.net> References: <1259024037.3871.36.camel@palomino.walls.org> <4B0E8B32.3020509@redhat.com> <1259264614.1781.47.camel@localhost> <6B4C84CD-F146-4B8B-A8BB-9963E0BA4C47@wilsonet.com> <1260240142.3086.14.camel@palomino.walls.org> <20091208042210.GA11147@core.coreip.homeip.net> Content-Type: text/plain Date: Tue, 08 Dec 2009 07:35:43 -0500 Message-Id: <1260275743.3094.6.camel@palomino.walls.org> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1923 Lines: 49 On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote: > On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote: > > So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the > > end of the month. > > > > I can setup the CX2388[58] hardware to look for both RC-5 and RC-6 with > > a common set of parameters, so I may be able to set up the decoders to > > handle decoding from two different remote types at once. The HVR boards > > can ship with either type of remote AFAIK. > > > > I wonder if I can flip the keytables on the fly or if I have to create > > two different input devices? > > > > Can you distinguish between the 2 remotes (not receivers)? Yes. RC-6 and RC-5 are different enough to distinguish between the two. (Honestly I could pile on more protocols that have similar pulse time periods, but that's complexity for no good reason and I don't know of a vendor that bundles 3 types of remotes per TV card.) > Like I said, > I think the preferred way is to represent every remote that can be > distinguished from each other as a separate input device. OK. With RC-5, NEC, and RC-6 at least there is also an address or system byte or word to distingish different remotes. However creating multiple input devices on the fly for detected remotes would be madness - especially with a decoding error in the address bits. Any one vendor usually picks one address for their bundled remote. Hauppaugue uses address 0x1e for it's RC-5 remotes AFAICT. > Applications > expect to query device capabilities and expect them to stay somewhat > stable (we do support keymap change but I don't think anyone expectes > flip-flopping). OK. -- 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/