From: Sean Young <sean@mess.org>
To: Matthias Reichl <hias@horus.com>
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: Mon, 1 Mar 2021 10:42:22 +0000 [thread overview]
Message-ID: <20210301104221.GA25883@gofer.mess.org> (raw)
In-Reply-To: <20210226135713.GA10226@camel2.lan>
Hi Hias,
On Fri, Feb 26, 2021 at 02:57:13PM +0100, Matthias Reichl wrote:
> On Wed, Feb 24, 2021 at 09:57:47AM +0000, Sean Young wrote:
> > That's a good point, that's probably the way to go. I'll have a look at
> > modifying my eeepc box.
>
> On a second thought it's probably a bit more involved than just
> connecting an IR photo diode/transistor. CIRRX is a digital input
> and to get acceptable performance we'd also need an AGC circuit
> and a comparator / schmitt-trigger.
Yes, I had been thinking about building something like this.
> It might be easier to just feed a modulated digital signal into CIRRX,
> either from CIRTX or from a RPi running pwm-ir-tx.
That's a great idea, I hadn't thought of that. That's a lot easier!
> > Having said that, if all the hardware out there uses TSOP-type IR
> > receivers, I'm not sure how much use there is having this hooked up in
> > the driver; same for transmit.
>
> If it's not too much hassle I'd vote for keeping the RX demodulation
> feature in the driver - it's an interesting feature and might come in
> handy at times.
It's kind of interesting, I agree.
> For TX we need to keep carrier function as CIRTX always transmits
> modulated singals according to the IT8712 datasheet (unmodulated TX
> output would be quite odd, haven't seen that yet).
There are IR signals which are unmodulated. In IRP this would start
with {0k, and there are several of such protocols: Jerrold, Revox for
example:
http://www.hifi-remote.com/wiki/index.php/Revox
I never seen such hardware and I have no idea how well this works in
practise.
Sean
prev parent reply other threads:[~2021-03-01 10:43 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
2021-02-24 9:57 ` Sean Young
2021-02-26 13:57 ` Matthias Reichl
2021-03-01 10:42 ` Sean Young [this message]
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=20210301104221.GA25883@gofer.mess.org \
--to=sean@mess.org \
--cc=hias@horus.com \
--cc=linux-media@vger.kernel.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.