2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2017-07-03 03:37:58 +08:00
|
|
|
|
|
|
|
|
menuconfig RC_CORE
|
|
|
|
|
tristate "Remote Controller support"
|
2009-12-11 19:00:00 +08:00
|
|
|
depends on INPUT
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2017-07-03 03:37:58 +08:00
|
|
|
Enable support for Remote Controllers on Linux. This is
|
|
|
|
|
needed in order to support several video capture adapters,
|
|
|
|
|
standalone IR receivers/transmitters, and RF receivers.
|
|
|
|
|
|
|
|
|
|
Enable this option if you have a video capture board even
|
|
|
|
|
if you don't need IR, as otherwise, you may not be able to
|
|
|
|
|
compile the driver for your adapter.
|
2010-08-09 21:07:20 +08:00
|
|
|
|
2017-07-03 03:37:58 +08:00
|
|
|
Say Y when you have a TV or an IR device.
|
|
|
|
|
|
|
|
|
|
if RC_CORE
|
2010-07-03 12:06:57 +08:00
|
|
|
|
2018-05-27 19:24:09 +08:00
|
|
|
config BPF_LIRC_MODE2
|
|
|
|
|
bool "Support for eBPF programs attached to lirc devices"
|
|
|
|
|
depends on BPF_SYSCALL
|
|
|
|
|
depends on RC_CORE=y
|
|
|
|
|
depends on LIRC
|
|
|
|
|
help
|
|
|
|
|
Allow attaching eBPF programs to a lirc device using the bpf(2)
|
|
|
|
|
syscall command BPF_PROG_ATTACH. This is supported for raw IR
|
|
|
|
|
receivers.
|
|
|
|
|
|
|
|
|
|
These eBPF programs can be used to decode IR into scancodes, for
|
|
|
|
|
IR protocols not supported by the kernel decoders.
|
|
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config LIRC
|
|
|
|
|
bool "LIRC user interface"
|
|
|
|
|
help
|
|
|
|
|
Enable this option to enable the Linux Infrared Remote
|
|
|
|
|
Control user interface (e.g. /dev/lirc*). This interface
|
|
|
|
|
passes raw IR to and from userspace, which is needed for
|
|
|
|
|
IR transmitting (aka "blasting") and for the lirc daemon.
|
|
|
|
|
|
|
|
|
|
source "drivers/media/rc/keymaps/Kconfig"
|
|
|
|
|
|
2017-09-23 22:41:13 +08:00
|
|
|
menuconfig RC_DECODERS
|
2018-01-04 19:47:28 +08:00
|
|
|
bool "Remote controller decoders"
|
2012-07-06 20:21:13 +08:00
|
|
|
|
2017-09-23 22:41:13 +08:00
|
|
|
if RC_DECODERS
|
2022-03-14 18:01:05 +08:00
|
|
|
|
|
|
|
|
config IR_IMON_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the iMON protocol"
|
|
|
|
|
help
|
|
|
|
|
Enable this option if you have iMON PAD or Antec Veris infrared
|
|
|
|
|
remote control and you would like to use it with a raw IR
|
|
|
|
|
receiver, or if you wish to use an encoder to transmit this IR.
|
|
|
|
|
|
|
|
|
|
config IR_JVC_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the JVC protocol"
|
|
|
|
|
select BITREVERSE
|
|
|
|
|
|
|
|
|
|
help
|
|
|
|
|
Enable this option if you have an infrared remote control which
|
|
|
|
|
uses the JVC protocol, and you need software decoding support.
|
|
|
|
|
|
|
|
|
|
config IR_MCE_KBD_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
|
|
|
|
|
select BITREVERSE
|
|
|
|
|
|
|
|
|
|
help
|
|
|
|
|
Enable this option if you have a Microsoft Remote Keyboard for
|
|
|
|
|
Windows Media Center Edition, which you would like to use with
|
|
|
|
|
a raw IR receiver in your system.
|
|
|
|
|
|
2010-03-25 07:47:53 +08:00
|
|
|
config IR_NEC_DECODER
|
2010-04-09 20:20:11 +08:00
|
|
|
tristate "Enable IR raw decoder for the NEC protocol"
|
2010-05-15 01:09:57 +08:00
|
|
|
select BITREVERSE
|
2010-03-25 07:47:53 +08:00
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-03-25 07:47:53 +08:00
|
|
|
Enable this option if you have IR with NEC protocol, and
|
|
|
|
|
if the IR is decoded in software
|
2010-04-04 21:27:20 +08:00
|
|
|
|
|
|
|
|
config IR_RC5_DECODER
|
2010-04-09 20:20:11 +08:00
|
|
|
tristate "Enable IR raw decoder for the RC-5 protocol"
|
2010-05-27 01:08:51 +08:00
|
|
|
select BITREVERSE
|
2010-04-04 21:27:20 +08:00
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-04-04 21:27:20 +08:00
|
|
|
Enable this option if you have IR with RC-5 protocol, and
|
|
|
|
|
if the IR is decoded in software
|
2010-04-09 07:04:40 +08:00
|
|
|
|
|
|
|
|
config IR_RC6_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the RC6 protocol"
|
2010-05-27 01:08:51 +08:00
|
|
|
select BITREVERSE
|
2010-04-09 07:04:40 +08:00
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-04-09 07:04:40 +08:00
|
|
|
Enable this option if you have an infrared remote control which
|
|
|
|
|
uses the RC6 protocol, and you need software decoding support.
|
2010-04-17 05:29:02 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_RCMM_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the RC-MM protocol"
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2022-03-14 18:01:05 +08:00
|
|
|
Enable this option when you have IR with RC-MM protocol, and
|
|
|
|
|
you need the software decoder. The driver supports 12,
|
|
|
|
|
24 and 32 bits RC-MM variants. You can enable or disable the
|
|
|
|
|
different modes using the following RC protocol keywords:
|
|
|
|
|
'rc-mm-12', 'rc-mm-24' and 'rc-mm-32'.
|
2010-04-16 05:46:10 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called ir-rcmm-decoder.
|
2010-04-16 05:46:10 +08:00
|
|
|
|
2011-11-23 23:04:08 +08:00
|
|
|
config IR_SANYO_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the Sanyo protocol"
|
2020-12-04 07:17:03 +08:00
|
|
|
select BITREVERSE
|
2011-11-23 23:04:08 +08:00
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2011-11-23 23:04:08 +08:00
|
|
|
Enable this option if you have an infrared remote control which
|
|
|
|
|
uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
|
|
|
|
|
and you need software decoding support.
|
|
|
|
|
|
2014-01-17 21:58:48 +08:00
|
|
|
config IR_SHARP_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the Sharp protocol"
|
2020-12-04 07:17:03 +08:00
|
|
|
select BITREVERSE
|
2014-01-17 21:58:48 +08:00
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2014-01-17 21:58:48 +08:00
|
|
|
Enable this option if you have an infrared remote control which
|
2015-10-30 03:28:08 +08:00
|
|
|
uses the Sharp protocol (Sharp, Denon), and you need software
|
|
|
|
|
decoding support.
|
2014-01-17 21:58:48 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_SONY_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the Sony protocol"
|
[media] rc-core support for Microsoft IR keyboard/mouse
This is a custom IR protocol decoder, for the RC-6-ish protocol used by
the Microsoft Remote Keyboard, apparently developed internally at
Microsoft, and officially dubbed MCIR-2, per their March 2011 remote and
transceiver requirements and specifications document, which also touches
on this IR keyboard/mouse device.
Its a standard keyboard with embedded thumb stick mouse pointer and
mouse buttons, along with a number of media keys. The media keys are
standard RC-6, identical to the signals from the stock MCE remotes, and
will be handled as such. The keyboard and mouse signals will be decoded
and delivered to the system by an input device registered specifically
by this driver.
Successfully tested with multiple mceusb-driven transceivers, as well as
with fintek-cir and redrat3 hardware. Essentially, any raw IR hardware
with enough sampling resolution should be able to use this decoder,
nothing about it is at all receiver-hardware-specific.
This work is inspired by lirc_mod_mce:
The documentation there and code aided in understanding and decoding the
protocol, but the bulk of the code is actually borrowed more from the
existing in-kernel decoders than anything. I did recycle the keyboard
keycode table, a few defines, and some of the keyboard and mouse data
parsing bits from lirc_mod_mce though.
Special thanks to James Meyer for providing the hardware, and being
patient with me as I took forever to get around to writing this.
callback routine to ensure we don't get any stuck keys, and used
symbolic names for the keytable. Also cc'ing Florian this time, who I
believe is the original mod-mce author...
CC: Florian Demski <fdemski@users.sourceforge.net>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-07-14 05:09:48 +08:00
|
|
|
select BITREVERSE
|
|
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2022-03-14 18:01:05 +08:00
|
|
|
Enable this option if you have an infrared remote control which
|
|
|
|
|
uses the Sony protocol, and you need software decoding support.
|
2014-07-27 04:28:26 +08:00
|
|
|
|
|
|
|
|
config IR_XMP_DECODER
|
|
|
|
|
tristate "Enable IR raw decoder for the XMP protocol"
|
|
|
|
|
select BITREVERSE
|
|
|
|
|
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2014-07-27 04:28:26 +08:00
|
|
|
Enable this option if you have IR with XMP protocol, and
|
|
|
|
|
if the IR is decoded in software
|
2017-12-04 00:06:54 +08:00
|
|
|
|
2012-07-06 20:12:59 +08:00
|
|
|
endif #RC_DECODERS
|
[media] rc-core support for Microsoft IR keyboard/mouse
This is a custom IR protocol decoder, for the RC-6-ish protocol used by
the Microsoft Remote Keyboard, apparently developed internally at
Microsoft, and officially dubbed MCIR-2, per their March 2011 remote and
transceiver requirements and specifications document, which also touches
on this IR keyboard/mouse device.
Its a standard keyboard with embedded thumb stick mouse pointer and
mouse buttons, along with a number of media keys. The media keys are
standard RC-6, identical to the signals from the stock MCE remotes, and
will be handled as such. The keyboard and mouse signals will be decoded
and delivered to the system by an input device registered specifically
by this driver.
Successfully tested with multiple mceusb-driven transceivers, as well as
with fintek-cir and redrat3 hardware. Essentially, any raw IR hardware
with enough sampling resolution should be able to use this decoder,
nothing about it is at all receiver-hardware-specific.
This work is inspired by lirc_mod_mce:
The documentation there and code aided in understanding and decoding the
protocol, but the bulk of the code is actually borrowed more from the
existing in-kernel decoders than anything. I did recycle the keyboard
keycode table, a few defines, and some of the keyboard and mouse data
parsing bits from lirc_mod_mce though.
Special thanks to James Meyer for providing the hardware, and being
patient with me as I took forever to get around to writing this.
callback routine to ensure we don't get any stuck keys, and used
symbolic names for the keytable. Also cc'ing Florian this time, who I
believe is the original mod-mce author...
CC: Florian Demski <fdemski@users.sourceforge.net>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-07-14 05:09:48 +08:00
|
|
|
|
2012-05-28 19:17:47 +08:00
|
|
|
menuconfig RC_DEVICES
|
|
|
|
|
bool "Remote Controller devices"
|
|
|
|
|
|
|
|
|
|
if RC_DEVICES
|
|
|
|
|
|
2010-10-09 03:23:56 +08:00
|
|
|
config IR_ENE
|
2010-09-07 05:26:11 +08:00
|
|
|
tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
|
2018-04-21 01:42:49 +08:00
|
|
|
depends on PNP || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-10-09 03:23:56 +08:00
|
|
|
Say Y here to enable support for integrated infrared receiver
|
2010-09-07 05:26:11 +08:00
|
|
|
/transceiver made by ENE.
|
2010-10-09 03:23:56 +08:00
|
|
|
|
|
|
|
|
You can see if you have it by looking at lspnp output.
|
2010-09-07 05:26:11 +08:00
|
|
|
Output should include ENE0100 ENE0200 or something similar.
|
2010-10-09 03:23:56 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ene_ir.
|
|
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_FINTEK
|
|
|
|
|
tristate "Fintek Consumer Infrared Transceiver"
|
|
|
|
|
depends on PNP || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable support for integrated infrared receiver
|
|
|
|
|
/transceiver made by Fintek. This chip is found on assorted
|
|
|
|
|
Jetway motherboards (and of course, possibly others).
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called fintek-cir.
|
|
|
|
|
|
|
|
|
|
config IR_GPIO_CIR
|
|
|
|
|
tristate "GPIO IR remote control"
|
|
|
|
|
depends on (OF && GPIOLIB) || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to use GPIO based IR Receiver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called gpio-ir-recv.
|
|
|
|
|
|
|
|
|
|
config IR_GPIO_TX
|
|
|
|
|
tristate "GPIO IR Bit Banging Transmitter"
|
|
|
|
|
depends on LIRC
|
|
|
|
|
depends on (OF && GPIOLIB) || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to a GPIO based IR transmitter. This is a
|
|
|
|
|
bit banging driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called gpio-ir-tx.
|
|
|
|
|
|
2014-08-31 10:39:10 +08:00
|
|
|
config IR_HIX5HD2
|
|
|
|
|
tristate "Hisilicon hix5hd2 IR remote control"
|
2021-11-09 20:55:20 +08:00
|
|
|
depends on (OF && HAS_IOMEM) || COMPILE_TEST
|
2014-08-31 10:39:10 +08:00
|
|
|
help
|
2017-04-20 07:13:54 +08:00
|
|
|
Say Y here if you want to use hisilicon hix5hd2 remote control.
|
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called ir-hix5hd2.
|
2014-08-31 10:39:10 +08:00
|
|
|
|
2017-04-20 07:13:54 +08:00
|
|
|
If you're not sure, select N here
|
2014-08-31 10:39:10 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_IGORPLUGUSB
|
|
|
|
|
tristate "IgorPlug-USB IR Receiver"
|
|
|
|
|
depends on USB
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use the IgorPlug-USB IR Receiver by
|
|
|
|
|
Igor Cesko. This device is included on the Fit-PC2.
|
|
|
|
|
|
|
|
|
|
Note that this device can only record bursts of 36 IR pulses and
|
|
|
|
|
spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called igorplugusb.
|
|
|
|
|
|
|
|
|
|
config IR_IGUANA
|
|
|
|
|
tristate "IguanaWorks USB IR Transceiver"
|
|
|
|
|
depends on USB
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use the IguanaWorks USB IR Transceiver.
|
|
|
|
|
Both infrared receive and send are supported. If you want to
|
|
|
|
|
change the ID or the pin config, use the user space driver from
|
|
|
|
|
IguanaWorks.
|
|
|
|
|
|
|
|
|
|
Only firmware 0x0205 and later is supported.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called iguanair.
|
|
|
|
|
|
2010-04-17 05:29:02 +08:00
|
|
|
config IR_IMON
|
|
|
|
|
tristate "SoundGraph iMON Receiver and Display"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-04-17 05:29:02 +08:00
|
|
|
Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
|
|
|
|
|
IR Receiver and/or LCD/VFD/VGA display.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called imon.
|
2010-06-02 04:32:08 +08:00
|
|
|
|
2018-01-06 03:58:51 +08:00
|
|
|
config IR_IMON_RAW
|
|
|
|
|
tristate "SoundGraph iMON Receiver (early raw IR models)"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2018-01-06 03:58:51 +08:00
|
|
|
Say Y here if you want to use a SoundGraph iMON IR Receiver,
|
|
|
|
|
early raw models.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called imon_raw.
|
|
|
|
|
|
2011-03-17 04:14:52 +08:00
|
|
|
config IR_ITE_CIR
|
|
|
|
|
tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
|
2018-04-21 01:42:49 +08:00
|
|
|
depends on PNP || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2011-03-17 04:14:52 +08:00
|
|
|
Say Y here to enable support for integrated infrared receivers
|
|
|
|
|
/transceivers made by ITE Tech Inc. These are found in
|
|
|
|
|
several ASUS devices, like the ASUS Digimatrix or the ASUS
|
|
|
|
|
EEEBox 1501U.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ite-cir.
|
|
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_MCEUSB
|
|
|
|
|
tristate "Windows Media Center Ed. eHome Infrared Transceiver"
|
|
|
|
|
depends on USB
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2022-03-14 18:01:05 +08:00
|
|
|
Say Y here if you want to use a Windows Media Center Edition
|
|
|
|
|
eHome Infrared Transceiver.
|
[media] fintek-cir: new driver for Fintek LPC SuperIO CIR function
This is a new driver for the Fintek LPC SuperIO CIR function, in the
Fintek F71809 chip. Hardware and datasheets were provided by Fintek, so
thanks go to them for supporting this effort.
This driver started out as a copy of the nuvoton-cir driver, and was
then modified as needed for the Fintek chip. The two share many
similaries, though the buffer handling for the Fintek chip is actually
nearly identical to the mceusb buffer handling, so the parser routine is
almost a drop-in copy of the mceusb buffer parser (a candidate for being
abstracted out into shared code at some point).
This initial code drop *only* supports receive, but the hardware does
support transmit as well. I really haven't even started to look at
what's required, but my guess is that its also pretty similar to mceusb.
Most people are probably only really interested in RX anyway though, so
I think its good to get this out there even with only RX.
(Nb: there are also Fintek-made mceusb receivers, which presumably, this
chip shares CIR hardware with).
This hardware can be found on at least Jetway NC98 boards and derivative
systems, and likely others as well. Functionality was tested with an
NC98 development board, in-kernel decode of RC6 (mce), RC5 (hauppauge)
and NEC-ish (tivo) remotes all successful, as was lirc userspace decode
of the RC6 remote.
CC: Aaron Huang <aaron_huang@fintek.com.tw>
CC: Tom Tsai <tom_tsai@fintek.com.tw>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-05-26 00:35:13 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
2022-03-14 18:01:05 +08:00
|
|
|
module will be called mceusb.
|
[media] fintek-cir: new driver for Fintek LPC SuperIO CIR function
This is a new driver for the Fintek LPC SuperIO CIR function, in the
Fintek F71809 chip. Hardware and datasheets were provided by Fintek, so
thanks go to them for supporting this effort.
This driver started out as a copy of the nuvoton-cir driver, and was
then modified as needed for the Fintek chip. The two share many
similaries, though the buffer handling for the Fintek chip is actually
nearly identical to the mceusb buffer handling, so the parser routine is
almost a drop-in copy of the mceusb buffer parser (a candidate for being
abstracted out into shared code at some point).
This initial code drop *only* supports receive, but the hardware does
support transmit as well. I really haven't even started to look at
what's required, but my guess is that its also pretty similar to mceusb.
Most people are probably only really interested in RX anyway though, so
I think its good to get this out there even with only RX.
(Nb: there are also Fintek-made mceusb receivers, which presumably, this
chip shares CIR hardware with).
This hardware can be found on at least Jetway NC98 boards and derivative
systems, and likely others as well. Functionality was tested with an
NC98 development board, in-kernel decode of RC6 (mce), RC5 (hauppauge)
and NEC-ish (tivo) remotes all successful, as was lirc userspace decode
of the RC6 remote.
CC: Aaron Huang <aaron_huang@fintek.com.tw>
CC: Tom Tsai <tom_tsai@fintek.com.tw>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-05-26 00:35:13 +08:00
|
|
|
|
2014-11-19 04:22:34 +08:00
|
|
|
config IR_MESON
|
|
|
|
|
tristate "Amlogic Meson IR remote receiver"
|
|
|
|
|
depends on ARCH_MESON || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2014-11-19 04:22:34 +08:00
|
|
|
Say Y if you want to use the IR remote receiver available
|
|
|
|
|
on Amlogic Meson SoCs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called meson-ir.
|
|
|
|
|
|
2021-07-20 01:05:06 +08:00
|
|
|
config IR_MESON_TX
|
|
|
|
|
tristate "Amlogic Meson IR TX"
|
|
|
|
|
depends on ARCH_MESON || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to use the IR transmitter available on
|
|
|
|
|
Amlogic Meson SoCs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called meson-ir-tx.
|
|
|
|
|
|
2017-01-13 15:35:39 +08:00
|
|
|
config IR_MTK
|
|
|
|
|
tristate "Mediatek IR remote receiver"
|
|
|
|
|
depends on ARCH_MEDIATEK || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2017-01-13 15:35:39 +08:00
|
|
|
Say Y if you want to use the IR remote receiver available
|
|
|
|
|
on Mediatek SoCs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called mtk-cir.
|
|
|
|
|
|
2010-10-09 03:23:56 +08:00
|
|
|
config IR_NUVOTON
|
|
|
|
|
tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
|
2018-04-21 01:42:49 +08:00
|
|
|
depends on PNP || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-07-31 22:59:26 +08:00
|
|
|
Say Y here to enable support for integrated infrared receiver
|
2019-02-19 03:29:01 +08:00
|
|
|
/transceiver made by Nuvoton (formerly Winbond). This chip is
|
2010-10-09 03:23:56 +08:00
|
|
|
found in the ASRock ION 330HT, as well as assorted Intel
|
|
|
|
|
DP55-series motherboards (and of course, possibly others).
|
2010-07-31 22:59:26 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
2010-10-09 03:23:56 +08:00
|
|
|
module will be called nuvoton-cir.
|
2010-07-31 22:59:26 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_PWM_TX
|
|
|
|
|
tristate "PWM IR transmitter"
|
|
|
|
|
depends on LIRC
|
|
|
|
|
depends on PWM
|
|
|
|
|
depends on OF || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to use a PWM based IR transmitter. This is
|
|
|
|
|
more power efficient than the bit banging gpio driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called pwm-ir-tx.
|
|
|
|
|
|
[media] redrat3: new rc-core IR transceiver device driver
This is a new rc-core device driver for the IR transceivers made by
RedRat Ltd. (http://redrat.co.uk/). It started out life as an
out-of-lirc-tree lirc driver, maintained in its own repo on sourceforge,
by Stephen Cox. He started porting it to what was then ir-core, and I
finally picked it up about two week ago and did a fairly large overhaul
on it, and its now into a state where I'm fairly comfortable submitting
it here for review and inclusion in the kernel. I'm claiming authorship
of this driver, since while it started out as Stephen's work, its
definitely a derivative work now, at 876 lines added and 1698 lines
removed since grabbing it from sourceforge. Stephen's name is retained
as secondary author though, and credited in the headers. Those
interested in seeing how the changes evolved can (at least for now) look
at this branch in my git tree:
http://git.kernel.org/?p=linux/kernel/git/jarod/linux-2.6-ir.git;a=shortlog;h=refs/heads/redrat3
That won't be around forever though, and I'm doing this as a single
commit to go into mainline. Anyway...
I've successfully tested in-kernel decode of rc5, rc6 and nec remotes,
as well as lirc userspace decode of rc5 and rc6. There are still some
quirks here to sort out with rc5 lirc userspace decode, but I'm working
with the RedRat folks themselves to figure out what's going on there
(rc5 lirc decode works, but you only get an event on key release --
in-kernel rc5 decode behaves perfectly fine). Note that lirc decode of
rc6 is working perfectly. Transmit is also working, tested by pointing
the redrat3 at an mceusb transceiver, which happily picked up the
transmitted signals and properly decoded them.
There's no default remote for this hardware, so its somewhat arbitrarily
set to use the Hauppauge RC5 keymap by default. Easily changed out by
way of ir-keytable and irrelevant if you're using lircd for decode.
CC: Chris Dodge <chris@redrat.co.uk>
CC: Andrew Vincer <Andrew.Vincer@redrat.co.uk>
CC: Stephen Cox <scox_nz@yahoo.com>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-05-05 01:02:42 +08:00
|
|
|
config IR_REDRAT3
|
|
|
|
|
tristate "RedRat3 IR Transceiver"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2013-07-31 06:00:04 +08:00
|
|
|
select NEW_LEDS
|
|
|
|
|
select LEDS_CLASS
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
[media] redrat3: new rc-core IR transceiver device driver
This is a new rc-core device driver for the IR transceivers made by
RedRat Ltd. (http://redrat.co.uk/). It started out life as an
out-of-lirc-tree lirc driver, maintained in its own repo on sourceforge,
by Stephen Cox. He started porting it to what was then ir-core, and I
finally picked it up about two week ago and did a fairly large overhaul
on it, and its now into a state where I'm fairly comfortable submitting
it here for review and inclusion in the kernel. I'm claiming authorship
of this driver, since while it started out as Stephen's work, its
definitely a derivative work now, at 876 lines added and 1698 lines
removed since grabbing it from sourceforge. Stephen's name is retained
as secondary author though, and credited in the headers. Those
interested in seeing how the changes evolved can (at least for now) look
at this branch in my git tree:
http://git.kernel.org/?p=linux/kernel/git/jarod/linux-2.6-ir.git;a=shortlog;h=refs/heads/redrat3
That won't be around forever though, and I'm doing this as a single
commit to go into mainline. Anyway...
I've successfully tested in-kernel decode of rc5, rc6 and nec remotes,
as well as lirc userspace decode of rc5 and rc6. There are still some
quirks here to sort out with rc5 lirc userspace decode, but I'm working
with the RedRat folks themselves to figure out what's going on there
(rc5 lirc decode works, but you only get an event on key release --
in-kernel rc5 decode behaves perfectly fine). Note that lirc decode of
rc6 is working perfectly. Transmit is also working, tested by pointing
the redrat3 at an mceusb transceiver, which happily picked up the
transmitted signals and properly decoded them.
There's no default remote for this hardware, so its somewhat arbitrarily
set to use the Hauppauge RC5 keymap by default. Easily changed out by
way of ir-keytable and irrelevant if you're using lircd for decode.
CC: Chris Dodge <chris@redrat.co.uk>
CC: Andrew Vincer <Andrew.Vincer@redrat.co.uk>
CC: Stephen Cox <scox_nz@yahoo.com>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-05-05 01:02:42 +08:00
|
|
|
Say Y here if you want to use a RedRat3 Infrared Transceiver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called redrat3.
|
|
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_RX51
|
|
|
|
|
tristate "Nokia N900 IR transmitter diode"
|
|
|
|
|
depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here if you want to enable support for the IR
|
|
|
|
|
transmitter diode built in the Nokia N900 (RX51) device.
|
|
|
|
|
|
|
|
|
|
The driver uses omap DM timers for generating the carrier
|
|
|
|
|
wave and pulses.
|
|
|
|
|
|
|
|
|
|
config IR_SERIAL
|
|
|
|
|
tristate "Homebrew Serial Port Receiver"
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to use Homebrew Serial Port Receivers and
|
|
|
|
|
Transceivers.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called serial-ir.
|
|
|
|
|
|
|
|
|
|
config IR_SERIAL_TRANSMITTER
|
|
|
|
|
bool "Serial Port Transmitter"
|
|
|
|
|
depends on IR_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Serial Port Transmitter support
|
|
|
|
|
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 14:12:18 +08:00
|
|
|
config IR_SPI
|
|
|
|
|
tristate "SPI connected IR LED"
|
|
|
|
|
depends on SPI && LIRC
|
2017-10-09 16:30:06 +08:00
|
|
|
depends on OF || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 14:12:18 +08:00
|
|
|
Say Y if you want to use an IR LED connected through SPI bus.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called ir-spi.
|
|
|
|
|
|
2010-08-03 02:46:03 +08:00
|
|
|
config IR_STREAMZAP
|
|
|
|
|
tristate "Streamzap PC Remote IR Receiver"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-08-03 02:46:03 +08:00
|
|
|
Say Y here if you want to use a Streamzap PC Remote
|
|
|
|
|
Infrared Receiver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called streamzap.
|
2010-07-31 22:59:14 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_SUNXI
|
|
|
|
|
tristate "SUNXI IR remote control"
|
|
|
|
|
depends on ARCH_SUNXI || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2022-03-14 18:01:05 +08:00
|
|
|
Say Y if you want to use sunXi internal IR Controller
|
2014-10-24 04:58:22 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
2022-03-14 18:01:05 +08:00
|
|
|
be called sunxi-ir.
|
2014-10-24 04:58:22 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_TOY
|
|
|
|
|
tristate "Infrared Toy and IR Droid"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2022-03-14 18:01:05 +08:00
|
|
|
Say Y here if you want to use the Infrared Toy or IR Droid, USB
|
|
|
|
|
versions.
|
2012-07-16 00:31:00 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called ir_toy.
|
2012-07-16 00:31:00 +08:00
|
|
|
|
2012-08-13 19:59:46 +08:00
|
|
|
config IR_TTUSBIR
|
|
|
|
|
tristate "TechnoTrend USB IR Receiver"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2012-08-13 19:59:46 +08:00
|
|
|
select NEW_LEDS
|
|
|
|
|
select LEDS_CLASS
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2012-08-13 19:59:46 +08:00
|
|
|
Say Y here if you want to use the TechnoTrend USB IR Receiver. The
|
|
|
|
|
driver can control the led.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called ttusbir.
|
|
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config IR_WINBOND_CIR
|
|
|
|
|
tristate "Winbond IR remote control"
|
|
|
|
|
depends on (X86 && PNP) || COMPILE_TEST
|
|
|
|
|
select NEW_LEDS
|
|
|
|
|
select LEDS_CLASS
|
|
|
|
|
select BITREVERSE
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2022-03-14 18:01:05 +08:00
|
|
|
Say Y here if you want to use the IR remote functionality found
|
|
|
|
|
in some Winbond SuperI/O chips. Currently only the WPCD376I
|
|
|
|
|
chip is supported (included in some Intel Media series
|
|
|
|
|
motherboards).
|
2012-08-10 17:16:36 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called winbond_cir.
|
2012-08-10 17:16:36 +08:00
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
config RC_ATI_REMOTE
|
|
|
|
|
tristate "ATI / X10 based USB RF remote controls"
|
|
|
|
|
depends on USB
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use an X10 based USB remote control.
|
|
|
|
|
These are RF remotes with USB receivers.
|
|
|
|
|
|
|
|
|
|
Such devices include the ATI remote that comes with many of ATI's
|
|
|
|
|
All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
|
|
|
|
|
Medion RF remote, and SnapStream FireFly remote.
|
|
|
|
|
|
|
|
|
|
This driver provides mouse pointer, left and right mouse buttons,
|
|
|
|
|
and maps all the other remote buttons to keypress events.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called ati_remote.
|
2014-03-01 07:28:55 +08:00
|
|
|
|
2010-11-26 05:36:27 +08:00
|
|
|
config RC_LOOPBACK
|
|
|
|
|
tristate "Remote Control Loopback Driver"
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2010-11-26 05:36:27 +08:00
|
|
|
Say Y here if you want support for the remote control loopback
|
|
|
|
|
driver which allows TX data to be sent back as RX data.
|
|
|
|
|
This is mostly useful for debugging purposes.
|
|
|
|
|
|
|
|
|
|
If you're not sure, select N here.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called rc_loopback.
|
|
|
|
|
|
2013-10-18 17:01:14 +08:00
|
|
|
config RC_ST
|
|
|
|
|
tristate "ST remote control receiver"
|
2014-08-21 03:21:35 +08:00
|
|
|
depends on ARCH_STI || COMPILE_TEST
|
2019-03-20 18:39:44 +08:00
|
|
|
help
|
2015-06-09 21:54:53 +08:00
|
|
|
Say Y here if you want support for ST remote control driver
|
|
|
|
|
which allows both IR and UHF RX.
|
|
|
|
|
The driver passes raw pulse and space information to the LIRC decoder.
|
2013-10-18 17:01:14 +08:00
|
|
|
|
2015-06-09 21:54:53 +08:00
|
|
|
If you're not sure, select N here.
|
2013-10-18 17:01:14 +08:00
|
|
|
|
2018-10-10 00:02:11 +08:00
|
|
|
config RC_XBOX_DVD
|
|
|
|
|
tristate "Xbox DVD Movie Playback Kit"
|
2021-04-21 21:58:41 +08:00
|
|
|
depends on USB
|
2018-10-10 00:02:11 +08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to use the Xbox DVD Movie Playback Kit.
|
|
|
|
|
These are IR remotes with USB receivers for the Original Xbox (2001).
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called xbox_remote.
|
|
|
|
|
|
2022-03-14 18:01:05 +08:00
|
|
|
source "drivers/media/rc/img-ir/Kconfig"
|
2020-05-03 17:27:55 +08:00
|
|
|
|
2012-05-28 19:17:47 +08:00
|
|
|
endif #RC_DEVICES
|
2017-07-03 03:37:58 +08:00
|
|
|
|
|
|
|
|
endif #RC_CORE
|