Searched full:ir (Results 1 – 25 of 75) sorted by relevance
123
| /Documentation/devicetree/bindings/media/ |
| D | allwinner,sun4i-a10-ir.yaml | 4 $id: http://devicetree.org/schemas/media/allwinner,sun4i-a10-ir.yaml# 19 - const: allwinner,sun4i-a10-ir 20 - const: allwinner,sun5i-a13-ir 21 - const: allwinner,sun6i-a31-ir 24 - allwinner,suniv-f1c100s-ir 25 - allwinner,sun8i-a83t-ir 26 - allwinner,sun8i-r40-ir 27 - allwinner,sun50i-a64-ir 28 - allwinner,sun50i-h6-ir 29 - allwinner,sun50i-h616-ir [all …]
|
| D | amlogic,meson6-ir.yaml | 4 $id: http://devicetree.org/schemas/media/amlogic,meson6-ir.yaml# 7 title: Amlogic Meson IR remote control receiver 19 - amlogic,meson6-ir 20 - amlogic,meson8b-ir 21 - amlogic,meson-gxbb-ir 22 - amlogic,meson-s4-ir 24 - const: amlogic,meson-gx-ir 25 - const: amlogic,meson-gxbb-ir 44 ir-receiver@c8100480 { 45 compatible = "amlogic,meson6-ir";
|
| D | amlogic,meson-ir-tx.yaml | 5 $id: http://devicetree.org/schemas/media/amlogic,meson-ir-tx.yaml# 8 title: Amlogic Meson IR transmitter 14 Some Amlogic SoCs such as A311D and T950D4 have IR transmitter 16 sending IR signals with arbitrary carrier frequency and duty cycle. 21 - const: amlogic,meson-ir-tx 23 - const: amlogic,meson-g12a-ir-tx 24 - const: amlogic,meson-ir-tx 54 ir@ff80014c { 55 compatible = "amlogic,meson-g12a-ir-tx", "amlogic,meson-ir-tx";
|
| D | hix5hd2-ir.txt | 1 Device-Tree bindings for hix5hd2 ir IP 4 - compatible: Should contain "hisilicon,hix5hd2-ir", or: 5 - "hisilicon,hi3796cv300-ir" for Hi3796CV300 IR device. 20 ir: ir@f8001000 { 21 compatible = "hisilicon,hix5hd2-ir";
|
| D | gpio-ir-receiver.yaml | 4 $id: http://devicetree.org/schemas/media/gpio-ir-receiver.yaml# 7 title: GPIO Based IR receiver 17 const: gpio-ir-receiver 27 description: IR receiver can wake-up the system. 37 ir-receiver { 38 compatible = "gpio-ir-receiver";
|
| D | img-ir-rev1.txt | 1 * ImgTec Infrared (IR) decoder version 1 7 - compatible: Should be "img,ir-rev1" 28 ir@2006200 { 29 compatible = "img,ir-rev1";
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-dev-intro.rst | 10 a bi-directional interface for transporting raw IR and decoded scancodes 13 file_operations defined on it. With respect to transporting raw IR and 17 raw IR into scancodes. 24 rc rc0: lirc_dev: driver mceusb registered at minor = 0, raw IR receiver, raw IR transmitter 36 - ir-ctl: can receive raw IR and transmit IR, as well as query LIRC 39 - ir-keytable: can load keymaps; allows you to set IR kernel protocols; load 40 BPF IR decoders and test IR decoding. Some BPF IR decoders are also 49 LIRC supports some modes of receiving and sending IR codes, as shown 58 This mode is for both sending and receiving IR. 62 set to the :ref:`IR protocol <Remote_controllers_Protocols>`, and all other [all …]
|
| D | rc-tables.rst | 10 IR keycodes for different devices. This caused the same IR keyname to be 11 mapped completely differently on different IR devices. This resulted 12 that the same IR keyname to be mapped completely different on different 13 IR's. Due to that, V4L2 API now specifies a standard for mapping Media 14 keys on IR. 20 layer. This means that the IR key strokes will look like normal keyboard 30 .. flat-table:: IR default keymapping 42 - Key examples on IR 417 - IR Blue key 425 - IR Green Key [all …]
|
| D | rc-protos.rst | 9 IR is encoded as a series of pulses and spaces, using a protocol. These 14 Therefore out the output of the IR decoder is a scancode; a single u32 17 Other things can be encoded too. Some IR protocols encode a toggle bit; this 20 toggle bit will invert from one IR message to the next. 24 target set in IR. 32 This IR protocol uses manchester encoding to encode 14 bits. There is a 33 detailed description here https://www.sbprojects.net/knowledge/ir/rc5.php. 183 described here https://www.sbprojects.net/knowledge/ir/jvc.php. 186 and the command the higher 8 bits; this is reversed from IR order. 279 described here https://www.sbprojects.net/knowledge/ir/nec.php. Note [all …]
|
| D | lirc-get-timeout.rst | 15 range for IR receive. 41 there's no IR activity for a long time. This can help lircd in 42 detecting that a IR signal is finished and can speed up the decoding
|
| D | lirc-read.rst | 48 The mode :ref:`LIRC_MODE_MODE2 <lirc-mode-mode2>` is for raw IR, 49 in which packets containing an unsigned int value describing an IR signal are 55 :ref:`IR protocol <Remote_controllers_Protocols>`
|
| D | rc-intro.rst | 19 device, as the IR receiver (and/or transmitter) can be used in 20 conjunction with a wide variety of different IR remotes.
|
| D | lirc-set-send-carrier.rst | 13 LIRC_SET_SEND_CARRIER - Set send carrier used to modulate IR TX. 34 Set send carrier used to modulate IR PWM pulses and spaces.
|
| /Documentation/devicetree/bindings/leds/irled/ |
| D | pwm-ir-tx.yaml | 4 $id: http://devicetree.org/schemas/leds/irled/pwm-ir-tx.yaml# 7 title: IR LED connected through PWM pin 13 IR LED connected through PWM pin which is used as remote controller 19 - const: pwm-ir-tx 20 - const: nokia,n900-ir 35 compatible = "pwm-ir-tx";
|
| D | gpio-ir-tx.yaml | 4 $id: http://devicetree.org/schemas/leds/irled/gpio-ir-tx.yaml# 7 title: IR LED connected through GPIO pin 13 IR LED connected through GPIO pin which is used as remote controller 18 const: gpio-ir-tx 34 compatible = "gpio-ir-tx";
|
| D | ir-spi-led.yaml | 4 $id: http://devicetree.org/schemas/leds/irled/ir-spi-led.yaml# 7 title: IR LED connected through SPI bus 13 IR LED switch is connected to the MOSI line of the SPI device and the data 21 const: ir-spi-led 52 compatible = "ir-spi-led";
|
| /Documentation/admin-guide/media/ |
| D | remote-controller.rst | 13 them have a microprocessor that receives the IR carriers, convert into 25 - ir-keytable: provides a way to query the remote controller, list the 26 protocols it supports, enable in-kernel support for IR decoder or 29 - ir-ctl: provide tools to handle remote controllers that support raw mode 34 ir-kbd-i2c module. 48 `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_ ir-keytable.1 51 The ir-keytable tool is nice for trouble shooting, i.e. to check 62 linux input layer (via event device). It also supports receiving IR codes 69 Xorg recognizes several IR keycodes that have its numerical value lower 76 keytable in runtime. Please read ir-keytable.1 man page for details.
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-inzi.rst | 49 * - Ir\ :sub:`0,0` 50 - Ir\ :sub:`0,1` 51 - Ir\ :sub:`0,2` 61 - Ir\ :sub:`n-1,n-3` 62 - Ir\ :sub:`n-1,n-2` 63 - Ir\ :sub:`n-1,n-1`
|
| /Documentation/driver-api/media/ |
| D | rc-core.rst | 26 However, most of the remote controllers use infrared (IR) to transmit signals. 32 carrier. The carrier can be switched on or off by the IR transmitter 36 In other words, a typical IR transmission can be viewed as a sequence of 53 So, a simple IR receiver hardware will just provide a sequence of timings 63 The RC core also supports devices that have just IR emitters, 68 When the RC core receives events produced by ``RC_DRIVER_IR_RAW`` IR 69 receivers, it needs to decode the IR protocol, in order to obtain the 74 of the type ``RC_DRIVER_SCANCODE``, or via its IR decoders), it needs
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-isl29018 | 16 is less affected by the ambient IR noise variation. 19 0 Sensing IR from LED and ambient 20 1 Sensing IR from LED with ambient IR rejection
|
| /Documentation/driver-api/media/drivers/ |
| D | cx88-devel.rst | 52 Hauppauge WinTV cx88 IR information 66 GPIO 16(I believe) is tied to the IR port (if present). 90 You need to recover the actual RC5 bits out of the (oversampled) IR sensor 94 I'm pretty sure when no IR signal is present the receiver is always in a 96 as well. Remember, this is a free running sample of the IR receiver state 113 http://www.xs4all.nl/~sbp/knowledge/ir/rc5.htm
|
| /Documentation/devicetree/bindings/iio/health/ |
| D | maxim,max30102.yaml | 34 maxim,ir-led-current-microamp: 35 description: IR LED current. Each step is approximately 200 microamps. 71 maxim,ir-led-current-microamp = <7000>;
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | rohm,bu27008.yaml | 14 and IR) with four configurable channels. Red and green being always 15 available and two out of the rest three (blue, clear, IR) can be
|
| D | rohm,bu27010.yaml | 14 IR and flickering detection) with five configurable channels. Red, green 16 three (blue, clear, IR) can be selected to be simultaneously measured.
|
| /Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,vf610-mscm-ir.txt | 11 - compatible: "fsl,vf610-mscm-ir" 24 compatible = "fsl,vf610-mscm-ir";
|
123