Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932185AbZLHPlu (ORCPT ); Tue, 8 Dec 2009 10:41:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932138AbZLHPlt (ORCPT ); Tue, 8 Dec 2009 10:41:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:2829 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932119AbZLHPls (ORCPT ); Tue, 8 Dec 2009 10:41:48 -0500 Message-ID: <4B1E73A5.2040006@redhat.com> Date: Tue, 08 Dec 2009 13:41:25 -0200 From: Mauro Carvalho Chehab User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Krzysztof Halasa CC: Dmitry Torokhov , Jon Smirl , hermann pitton , Christoph Bartelmus , awalls@radix.net, j@jannau.net, jarod@redhat.com, jarod@wilsonet.com, kraxel@redhat.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, superm1@ubuntu.com Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? References: <9e4733910912041628g5bedc9d2jbee3b0861aeb5511@mail.gmail.com> <1260070593.3236.6.camel@pc07.localdom.local> <20091206065512.GA14651@core.coreip.homeip.net> <4B1B99A5.2080903@redhat.com> <9e4733910912060952h4aad49dake8e8486acb6566bc@mail.gmail.com> <9e4733910912061323x22c618ccyf6edcee5b021cbe3@mail.gmail.com> <4B1D934E.7030103@redhat.com> <20091208042340.GC11147@core.coreip.homeip.net> <4B1E3F7D.9070806@redhat.com> <4B1E5EFA.4020801@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 969 Lines: 26 Krzysztof Halasa wrote: > Mauro Carvalho Chehab writes: > >> The enable/disable protocol decoder enable/disable interface is needed anyway, >> due to the needs for the hardware IR decoders > > Why do they need it exactly? > The key tables say all they need I hope? You can't upload a key for an unsupported protocol. Also, provided that hardware decoders in general don't support decoding multiple protocols at the same time, it is needed to select what protocol it will be decoding. So, userspace needs to: - retrieve the list of the supported protocols; - identify if a given IR is capable of multiple protocols; - be able to select what protocol(s) decoder(s) will be enabled. Cheers, Mauro. -- 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/