From: Matthias Reichl <hias@horus.com>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org,
"Juan Jesús García de Soria" <skandalfo@gmail.com>
Subject: Re: [PATCH 0/6] media: ite-cir driver cleanups
Date: Tue, 23 Feb 2021 20:16:15 +0100 [thread overview]
Message-ID: <20210223191615.GA9243@lenny.lan> (raw)
In-Reply-To: <20210223175001.GA12871@gofer.mess.org>
Hi Sean,
On Tue, Feb 23, 2021 at 05:50:01PM +0000, Sean Young wrote:
> On Tue, Feb 23, 2021 at 05:13:07PM +0100, Matthias Reichl wrote:
> > I could only test receiving (don't have a transmitter on that PC)
> > and also couldn't test the carrier options (I'm using a demodulating
> > TSOP receiver here), but your changes look sane to me.
>
> I only have got an eeepc box, with the same limitations. Do you happen to
> know what hardware there is for this driver? It would be nice to test this
> properly.
>
> This is the only IR driver that can change the RX carrier range, so it's
> kinda interesting.
In the most recent bug report I got (about a month ago) the user was
using an intel NUC (NUC10i3FNH/NUC10i3FNB according to DMI):
https://forum.libreelec.tv/thread/23211-intel-nightly-build-problem-with-mce-remote/?postID=148823#post148823
I've also seen NUCs with Nuvoton CIR though and I suspect they'll
all probably have a demodulating receiver soldered directly to the
board, so probably not easy to tinker with (haven't checked though).
I have only an ancient Pentium 4 mainboard (Gigabyte 8IPE775) with
an IT8712 here. IR RX/TX and CIR RX/TX are all exposed on a header,
but the BIOS is somewhat odd and doesn't contain CIR on/off settings
or announce the CIR via ACPI. So I had to manually patch ACPI tables
to get that beast working.... ITE8713 pnpid was close enough (couldn't
find a datasheet for 8713, only 8712 - that does mention demodulating
though).
I don't think I have a simple IR diode or transistor here to easily
test that, only demodulating TSOPs (and some clones) - hooking that
up to the mainboard wouldn't be too hard.
so long,
Hias
next prev parent reply other threads:[~2021-02-23 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 10:43 [PATCH 0/6] media: ite-cir driver cleanups Sean Young
2021-02-22 10:43 ` [PATCH 1/6] media: ite-cir: remove unused fields Sean Young
2021-02-22 10:43 ` [PATCH 2/6] media: ite-cir: set parent device Sean Young
2021-02-22 10:43 ` [PATCH 3/6] media: ite-cir: use standard logging and reduce noise Sean Young
2021-02-22 10:43 ` [PATCH 4/6] media: ite-cir: carrier and duty cycle can be set via ioctl Sean Young
2021-02-22 10:43 ` [PATCH 5/6] media: ite-cir: move runtime information into driver data Sean Young
2021-02-22 10:43 ` [PATCH 6/6] media: ite-cir: check for receive overflow Sean Young
2021-02-23 16:13 ` [PATCH 0/6] media: ite-cir driver cleanups Matthias Reichl
2021-02-23 17:50 ` Sean Young
2021-02-23 19:16 ` Matthias Reichl [this message]
2021-02-24 9:57 ` Sean Young
2021-02-26 13:57 ` Matthias Reichl
2021-03-01 10:42 ` 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=20210223191615.GA9243@lenny.lan \
--to=hias@horus.com \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.org \
--cc=skandalfo@gmail.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.