From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Young Subject: Re: [PATCH v2 2/3] rc: Introduce hix5hd2 IR transmitter driver Date: Wed, 27 Aug 2014 14:15:09 +0100 Message-ID: <20140827131509.GA3195@gofer.mess.org> References: <1408613086-12538-1-git-send-email-zhangfei.gao@linaro.org> <1408613086-12538-3-git-send-email-zhangfei.gao@linaro.org> <20140821100739.GA3252@gofer.mess.org> <53FD9BB7.6080207@linaro.org> <20140827095106.GA2712@gofer.mess.org> <53FDAE94.8010404@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <53FDAE94.8010404@linaro.org> Sender: linux-media-owner@vger.kernel.org To: zhangfei Cc: Mauro Carvalho Chehab , David =?iso-8859-1?Q?H=E4rdeman?= , arnd@arndb.de, haifeng.yan@linaro.org, jchxue@gmail.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-media@vger.kernel.org, Guoxiong Yan List-Id: devicetree@vger.kernel.org On Wed, Aug 27, 2014 at 06:10:28PM +0800, zhangfei wrote: > On 08/27/2014 05:51 PM, Sean Young wrote: > >On Wed, Aug 27, 2014 at 04:49:59PM +0800, zhangfei wrote: > >>On 08/21/2014 06:07 PM, Sean Young wrote: > >IR. There is be no reason to run lircd if you use this method. > Do you mean kernel decoder is enough to cover? > We use user space lircd to cosider more flexibility, even some > non-standard protocol. Just out of interest, what flexibility does lircd offer which the kernel decoders do not? > Anyway both method can be supported, depending on whether setting > the optional property "linux,rc-map-name" or not. Great, thanks. Sean From mboxrd@z Thu Jan 1 00:00:00 1970 From: sean@mess.org (Sean Young) Date: Wed, 27 Aug 2014 14:15:09 +0100 Subject: [PATCH v2 2/3] rc: Introduce hix5hd2 IR transmitter driver In-Reply-To: <53FDAE94.8010404@linaro.org> References: <1408613086-12538-1-git-send-email-zhangfei.gao@linaro.org> <1408613086-12538-3-git-send-email-zhangfei.gao@linaro.org> <20140821100739.GA3252@gofer.mess.org> <53FD9BB7.6080207@linaro.org> <20140827095106.GA2712@gofer.mess.org> <53FDAE94.8010404@linaro.org> Message-ID: <20140827131509.GA3195@gofer.mess.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Aug 27, 2014 at 06:10:28PM +0800, zhangfei wrote: > On 08/27/2014 05:51 PM, Sean Young wrote: > >On Wed, Aug 27, 2014 at 04:49:59PM +0800, zhangfei wrote: > >>On 08/21/2014 06:07 PM, Sean Young wrote: > >IR. There is be no reason to run lircd if you use this method. > Do you mean kernel decoder is enough to cover? > We use user space lircd to cosider more flexibility, even some > non-standard protocol. Just out of interest, what flexibility does lircd offer which the kernel decoders do not? > Anyway both method can be supported, depending on whether setting > the optional property "linux,rc-map-name" or not. Great, thanks. Sean