From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: Franklin Meng <fmeng2002@yahoo.com>
Cc: Douglas Schilling <dougsland@gmail.com>,
maillist <linux-media@vger.kernel.org>
Subject: Re: [Patch] Kworld 315U remote support
Date: Mon, 08 Feb 2010 11:13:30 -0200 [thread overview]
Message-ID: <4B700DFA.2010902@gmail.com> (raw)
In-Reply-To: <19431.32442.qm@web32702.mail.mud.yahoo.com>
Franklin Meng wrote:
> This patch adds remote support for the Kworld 315U device
>
> Note: I believe I got most of the mappings correct. Though the
> source and shutdown button probably could be mapped to something
> better.
>
> To be done: Still need to get the Kworld analog patch resubmitted.
> There are still some stuff I want to test with the analog patch before
> I resubmit it. Hopefully this patch will work ok.
>
> Please let me know if there are any issues applying the patch
Hi Franklin,
Could you please add a table with the full scan code?
There are currently two examples of such tables:
ir_codes_rc5_hauppauge_new_table - for RC5 keycodes
ir_codes_nec_terratec_cinergy_xs_table - for NEC keycodes
Basically, a full scan code has a 2-byte code instead of 1-byte,
and you need to specify the protocol at the table, like:
struct ir_scancode_table ir_codes_nec_terratec_cinergy_xs_table = {
.scan = ir_codes_nec_terratec_cinergy_xs,
.size = ARRAY_SIZE(ir_codes_nec_terratec_cinergy_xs),
.ir_type = IR_TYPE_NEC,
};
The em28xx is already prepared to properly handle the protocol.
the advantage of using a full table is that it is easy to replace
the keytable and even the protocol if someone wants to use a different
Remote Controller to control the device.
As you've declared this xclk:
.xclk = EM28XX_XCLK_FREQUENCY_12MHZ,
I suspect that your keycode is of the type NEC.
Cheers,
Mauro
next prev parent reply other threads:[~2010-02-08 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 19:53 [Patch] Kworld 315U remote support Franklin Meng
2010-02-08 13:13 ` Mauro Carvalho Chehab [this message]
2010-02-10 18:53 ` Franklin Meng
2010-02-10 19:05 ` Mauro Carvalho Chehab
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=4B700DFA.2010902@gmail.com \
--to=maurochehab@gmail.com \
--cc=dougsland@gmail.com \
--cc=fmeng2002@yahoo.com \
--cc=linux-media@vger.kernel.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