From: "Måns Rullgård" <mans@mansr.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Sean Young <sean@mess.org>,
linux-media <linux-media@vger.kernel.org>,
Mason <slash.tmp@free.fr>
Subject: Re: [PATCH v3 2/2] media: rc: Add driver for tango HW IR decoder
Date: Thu, 21 Sep 2017 18:11:46 +0100 [thread overview]
Message-ID: <yw1xd16kf031.fsf@mansr.com> (raw)
In-Reply-To: <f510d7a6-0b6a-002b-3aad-7dd634392d07@sigmadesigns.com> (Marc Gonzalez's message of "Thu, 21 Sep 2017 18:09:24 +0200")
Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:
> On 21/09/2017 17:46, Måns Rullgård wrote:
>
>> Marc Gonzalez writes:
>>
>>> From: Mans Rullgard <mans@mansr.com>
>>>
>>> The tango HW IR decoder supports NEC, RC-5, RC-6 protocols.
>>>
>>> Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
>>
>> Have you been able to test all the protocols? Universal remotes usually
>> support something or other with each of them.
>
> I found the Great Pile of Remotes locked away in a drawer.
> Played "What kind of batteries do you eat?" for about an hour.
> And found several NEC remotes, one RC-5, and one RC-6.
> Repeats seem to be handled differently than for NEC.
> I'll take a closer look.
That's not surprising, seeing as the way repeats are transmitted differs
between protocols.
If you're new to IR remote controls, this site has some good
information:
http://www.sbprojects.com/knowledge/ir/index.php
--
Måns Rullgård
next prev parent reply other threads:[~2017-09-21 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 14:47 [PATCH v3 1/2] media: dt: bindings: Add binding for tango HW IR decoder Marc Gonzalez
2017-09-21 14:49 ` [PATCH v3 2/2] media: rc: Add driver " Marc Gonzalez
2017-09-21 15:46 ` Måns Rullgård
2017-09-21 16:09 ` Marc Gonzalez
2017-09-21 17:11 ` Måns Rullgård [this message]
2017-09-21 15:57 ` Sean Young
2017-09-21 16:20 ` Marc Gonzalez
2017-09-21 16:59 ` Sean Young
2017-09-21 16:59 ` Måns Rullgård
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=yw1xd16kf031.fsf@mansr.com \
--to=mans@mansr.com \
--cc=linux-media@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
--cc=sean@mess.org \
--cc=slash.tmp@free.fr \
/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.