From: Sean Young <sean@mess.org>
To: Kamil Debski <k.debski@samsung.com>
Cc: dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
m.szyprowski@samsung.com, mchehab@osg.samsung.com,
hverkuil@xs4all.nl, kyungmin.park@samsung.com,
Hans Verkuil <hansverk@cisco.com>
Subject: Re: [RFC 1/6] cec: add new driver for cec support.
Date: Tue, 30 Dec 2014 13:32:49 +0000 [thread overview]
Message-ID: <20141230133249.GA1566@gofer.mess.org> (raw)
In-Reply-To: <1419345142-3364-2-git-send-email-k.debski@samsung.com>
On Tue, Dec 23, 2014 at 03:32:17PM +0100, Kamil Debski wrote:
> +There are still a few todo's, the main one being the remote control support
> +feature of CEC. I need to research if that should be implemented via the
> +standard kernel remote control support.
I guess a new rc driver type RC_DRIVER_CEC should be introduced (existing
types are RC_DRIVER_IR_RAW and RC_DRIVER_SCANCODE). rc_register_device()
should not register the sysfs attributes specific for IR, but register
sysfs attributes for cec like a link to the device.
In addition there should be a new rc_type protocol RC_TYPE_CEC; now
rc_keydown_notimeout() can be called for each key press.
I guess a new keymap should exist too.
HTH
Sean
next prev parent reply other threads:[~2014-12-30 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 14:32 [RFC 0/6] HDMI-CEC framework Kamil Debski
2014-12-23 14:32 ` [RFC 1/6] cec: add new driver for cec support Kamil Debski
2014-12-30 13:32 ` Sean Young [this message]
2015-01-08 16:50 ` Kamil Debski
2015-01-12 11:45 ` Hans Verkuil
2015-01-12 11:48 ` Hans Verkuil
2014-12-23 14:32 ` [RFC 2/6] v4l2-subdev: add cec ops Kamil Debski
2014-12-23 14:32 ` [RFC 3/6] adv7604: add cec support Kamil Debski
2014-12-23 14:32 ` [RFC 4/6] adv7511: " Kamil Debski
2014-12-23 14:32 ` [RFC 5/6] s5p-cec: Add s5p-cec driver Kamil Debski
2014-12-23 14:32 ` [RFC 6/6] dts: add s5p-cec to exynos4412-odroidu3 Kamil Debski
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=20141230133249.GA1566@gofer.mess.org \
--to=sean@mess.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansverk@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@osg.samsung.com \
/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