From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: 3.9.2 kernel - IR / em28xx_rc broken?
Date: Sun, 19 May 2013 19:26:59 +0200 [thread overview]
Message-ID: <51990B63.5090402@googlemail.com> (raw)
In-Reply-To: <1368972692.46197.YahooMailNeo@web120301.mail.ne1.yahoo.com>
Am 19.05.2013 16:11, schrieb Chris Rankin:
> ----- Original Message -----
>
>> em28xx_ir_change_protocol() should be called at least twice:
>> First from em28xx_ir_init() with RC_BIT_UNKNOWN (initial configuration)
>> and later from the RC core with RC_BIT_RC5.
>> Can you confirm that ?
> Yes, it does appear to be called twice: first with *rc_type=1 and then later with *rc_type=8.
Good, that's how it should be.
> But that still doesn't seem to stop ir->rc_type being RC_BIT_UNKNOWN in em2874_polling_getkey().
Hmm... that's weird. Are you sure about that ? Is this really a 3.9.2
vanilla kernel ?
The code looks good, ir->rc_type is updated by
em2874_ir_change_protocol() when the protocol is changed.
I also tried to reproduce your problem with a em2884 device with a RC5
remote control a few minutes ago, but everything works as expected...
One thing I noticed is that in em28xx_ir_handle_key() ir->last_readcount
is reset to 0 for the em2874 and em2884.
I assume the same should be done for em28174, too...
Anyway, that's a separate issue and older kernels did the same.
Regards,
Frank
next prev parent reply other threads:[~2013-05-19 17:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 13:57 3.9.2 kernel - IR / em28xx_rc broken? Chris Rankin
2013-05-18 14:36 ` Frank Schäfer
2013-05-18 15:17 ` Chris Rankin
2013-05-18 16:58 ` Frank Schäfer
2013-05-18 21:02 ` Chris Rankin
2013-05-19 13:40 ` Frank Schäfer
2013-05-19 14:11 ` Chris Rankin
2013-05-19 17:26 ` Frank Schäfer [this message]
2013-05-19 19:59 ` Chris Rankin
2013-05-19 21:02 ` Frank Schäfer
2013-05-19 22:36 ` Chris Rankin
2013-05-19 23:04 ` Chris Rankin
2013-05-20 12:38 ` Frank Schäfer
2013-05-20 12:47 ` Frank Schäfer
2013-05-20 13:01 ` Chris Rankin
2013-05-20 13:43 ` Frank Schäfer
2013-05-20 14:51 ` Chris Rankin
2013-05-20 15:36 ` Frank Schäfer
2013-05-20 16:02 ` Chris Rankin
2013-06-13 10:39 ` Mauro Carvalho Chehab
2013-06-13 10:50 ` Mauro Carvalho Chehab
2013-05-20 0:45 ` Chris Rankin
2013-05-20 12:40 ` Frank Schäfer
2013-05-20 12:48 ` Chris Rankin
2013-05-18 21:11 ` Chris Rankin
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=51990B63.5090402@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=rankincj@yahoo.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 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.