From: "Måns Rullgård" <mans@mansr.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Sean Young <sean@mess.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media <linux-media@vger.kernel.org>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>,
Mason <slash.tmp@free.fr>
Subject: Re: [PATCH v1] media: rc: Add driver for tango IR decoder
Date: Tue, 19 Sep 2017 12:54:18 +0100 [thread overview]
Message-ID: <yw1x1sn2zyxh.fsf@mansr.com> (raw)
In-Reply-To: <f0fd5679-5e24-c0fc-e22a-6a819028baad@sigmadesigns.com> (Marc Gonzalez's message of "Tue, 19 Sep 2017 13:34:38 +0200")
Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:
> On 19/09/2017 11:48, Måns Rullgård wrote:
>
>> Did you test the NEC32 variant? I don't have anything that produces
>> such codes.
>
> I don't have a NEC32 IR remote control either.
>
> IIUC, NEC32 means 16-bit address and 16-bit command.
>
> I checked the RTL with a HW engineer. The HW block translates the IR
> pulses into logical 1s and 0s according to the protocol parameters,
> stuffs the logical bits into a register, and fires an IRQ when there
> are 32 bits available. The block doesn't care if the bits are significant
> or just checksums (that is left up to software).
In that case I suppose it ought to just work.
--
Måns Rullgård
next prev parent reply other threads:[~2017-09-19 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:18 [PATCH v1] media: rc: Add driver for tango IR decoder Marc Gonzalez
2017-09-18 15:33 ` Måns Rullgård
2017-09-19 8:45 ` Marc Gonzalez
2017-09-19 9:48 ` Måns Rullgård
2017-09-19 11:34 ` Marc Gonzalez
2017-09-19 11:54 ` Måns Rullgård [this message]
2017-09-19 11:53 ` Marc Gonzalez
2017-09-19 12:21 ` Måns Rullgård
2017-09-19 12:43 ` Marc Gonzalez
2017-09-19 14:32 ` Måns Rullgård
2017-09-21 11:19 ` Sean Young
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=yw1x1sn2zyxh.fsf@mansr.com \
--to=mans@mansr.com \
--cc=linux-media@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
--cc=mchehab@kernel.org \
--cc=sean@mess.org \
--cc=slash.tmp@free.fr \
--cc=thibaud_cornic@sigmadesigns.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