All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhangfei.gao@linaro.org (zhangfei)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] rc: Introduce hix5hd2 IR transmitter driver
Date: Wed, 27 Aug 2014 16:49:59 +0800	[thread overview]
Message-ID: <53FD9BB7.6080207@linaro.org> (raw)
In-Reply-To: <20140821100739.GA3252@gofer.mess.org>



On 08/21/2014 06:07 PM, Sean Young wrote:
> On Thu, Aug 21, 2014 at 05:24:44PM +0800, Zhangfei Gao wrote:
>> From: Guoxiong Yan <yanguoxiong@huawei.com>

>> +	rdev->driver_type = RC_DRIVER_IR_RAW;
>> +	rdev->allowed_protocols = RC_BIT_ALL;
>> +	rdev->priv = priv;
>> +	rdev->open = hix5hd2_ir_open;
>> +	rdev->close = hix5hd2_ir_close;
>> +	rdev->driver_name = IR_HIX5HD2_NAME;
>> +	rdev->map_name = RC_MAP_LIRC;
>
> I'm not sure RC_MAP_LIRC is appropriate. If the hardware has no implicit
> remote, can this be stored in device tree like the sunxi-cir.c driver does?

OK? got it.
Will set optional property "linux,rc-map-name" for the map_name.
We usually use user space lirc decoder, so this optional property may 
not need to be set in dts.

>
>> +	rdev->input_name = "Hisilicon hix5hd2 Remote Control Receiver";
>
> 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?

Thanks for the suggestion.

WARNING: multiple messages have this Message-ID (diff)
From: zhangfei <zhangfei.gao@linaro.org>
To: Sean Young <sean@mess.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 16:49:59 +0800	[thread overview]
Message-ID: <53FD9BB7.6080207@linaro.org> (raw)
In-Reply-To: <20140821100739.GA3252@gofer.mess.org>



On 08/21/2014 06:07 PM, Sean Young wrote:
> On Thu, Aug 21, 2014 at 05:24:44PM +0800, Zhangfei Gao wrote:
>> From: Guoxiong Yan <yanguoxiong@huawei.com>

>> +	rdev->driver_type = RC_DRIVER_IR_RAW;
>> +	rdev->allowed_protocols = RC_BIT_ALL;
>> +	rdev->priv = priv;
>> +	rdev->open = hix5hd2_ir_open;
>> +	rdev->close = hix5hd2_ir_close;
>> +	rdev->driver_name = IR_HIX5HD2_NAME;
>> +	rdev->map_name = RC_MAP_LIRC;
>
> I'm not sure RC_MAP_LIRC is appropriate. If the hardware has no implicit
> remote, can this be stored in device tree like the sunxi-cir.c driver does?

OK, got it.
Will set optional property "linux,rc-map-name" for the map_name.
We usually use user space lirc decoder, so this optional property may 
not need to be set in dts.

>
>> +	rdev->input_name = "Hisilicon hix5hd2 Remote Control Receiver";
>
> 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?

Thanks for the suggestion.

  reply	other threads:[~2014-08-27  8:49 UTC|newest]

Thread overview: 29+ 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 ` Zhangfei Gao
2014-08-21  9:24 ` [PATCH v2 1/3] rc: Add DT bindings for hix5hd2 Zhangfei Gao
2014-08-21  9:24   ` Zhangfei Gao
2014-08-21  9:24 ` [PATCH v2 2/3] rc: Introduce hix5hd2 IR transmitter driver Zhangfei Gao
2014-08-21  9:24   ` Zhangfei Gao
2014-08-21 10:07   ` Sean Young
2014-08-21 10:07     ` Sean Young
2014-08-21 10:07     ` Sean Young
2014-08-27  8:49     ` zhangfei [this message]
2014-08-27  8:49       ` zhangfei
2014-08-27  9:51       ` Sean Young
2014-08-27  9:51         ` Sean Young
2014-08-27 10:10         ` zhangfei
2014-08-27 10:10           ` zhangfei
2014-08-27 13:15           ` Sean Young
2014-08-27 13:15             ` Sean Young
2014-08-21  9:24 ` [PATCH v2 3/3] [media] rc: remove change_protocol in rc-ir-raw.c Zhangfei Gao
2014-08-21  9:24   ` Zhangfei Gao
2014-08-21  9:24   ` Zhangfei Gao
2014-08-21 11:50   ` Mauro Carvalho Chehab
2014-08-21 11:50     ` Mauro Carvalho Chehab
2014-08-21 11:50     ` Mauro Carvalho Chehab
2014-08-27  8:42     ` zhangfei
2014-08-27  8:42       ` zhangfei
2014-08-27 11:34       ` Mauro Carvalho Chehab
2014-08-27 11:34         ` Mauro Carvalho Chehab
2014-08-28  9:18         ` zhangfei
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=53FD9BB7.6080207@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.