From: Sean Young <sean@mess.org>
To: zhangfei <zhangfei.gao@linaro.org>
Cc: "Mauro Carvalho Chehab" <m.chehab@samsung.com>,
"David Härdeman" <david@hardeman.nu>,
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" <yanguoxiong@huawei.com>
Subject: Re: [PATCH v2 2/3] rc: Introduce hix5hd2 IR transmitter driver
Date: Wed, 27 Aug 2014 10:51:06 +0100 [thread overview]
Message-ID: <20140827095106.GA2712@gofer.mess.org> (raw)
In-Reply-To: <53FD9BB7.6080207@linaro.org>
On Wed, Aug 27, 2014 at 04:49:59PM +0800, zhangfei wrote:
> On 08/21/2014 06:07 PM, Sean Young wrote:
> >On Thu, Aug 21, 2014 at 05:24:44PM +0800, Zhangfei Gao wrote:
> >It would be useful is rdev->input_phys, rdev->input_id,
> >rdev->timeout, rdev->rx_resolution are set correctly.
>
> OK, will set rdev->timeout, rdev->rx_resolution
> Not sure the usage of rdev->input_id, why is it required?
This is for the EVIOCGID ioctl on the input device which will be created
for the rc device. This is used for delivering input events from decoded
IR. There is be no reason to run lircd if you use this method.
Sean
next prev parent reply other threads:[~2014-08-27 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 9:24 [PATCH v2 0/3] Introduce hix5hd2 IR transmitter driver Zhangfei Gao
2014-08-21 9:24 ` [PATCH v2 1/3] rc: Add DT bindings for hix5hd2 Zhangfei Gao
2014-08-21 9:24 ` [PATCH v2 2/3] rc: Introduce hix5hd2 IR transmitter driver Zhangfei Gao
2014-08-21 10:07 ` Sean Young
2014-08-27 8:49 ` zhangfei
2014-08-27 9:51 ` Sean Young [this message]
2014-08-27 10:10 ` zhangfei
2014-08-27 13:15 ` Sean Young
[not found] ` <1408613086-12538-1-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-08-21 9:24 ` [PATCH v2 3/3] [media] rc: remove change_protocol in rc-ir-raw.c Zhangfei Gao
2014-08-21 11:50 ` Mauro Carvalho Chehab
2014-08-27 8:42 ` zhangfei
2014-08-27 11:34 ` Mauro Carvalho Chehab
2014-08-28 9:18 ` zhangfei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140827095106.GA2712@gofer.mess.org \
--to=sean@mess.org \
--cc=arnd@arndb.de \
--cc=david@hardeman.nu \
--cc=devicetree@vger.kernel.org \
--cc=haifeng.yan@linaro.org \
--cc=jchxue@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=yanguoxiong@huawei.com \
--cc=zhangfei.gao@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).