Home
last modified time | relevance | path

Searched refs:IR (Results 1 – 25 of 91) sorted by relevance

1234

/linux-6.1.9/arch/sparc/math-emu/
Dmath_64.c184 int IR; in do_mathemu() local
262 IR = 2; in do_mathemu()
277 IR = 0; in do_mathemu()
280 case 1: if (XR) IR = 1; break; /* Not Equal */ in do_mathemu()
281 case 2: if (XR == 1 || XR == 2) IR = 1; break; /* Less or Greater */ in do_mathemu()
282 case 3: if (XR & 1) IR = 1; break; /* Unordered or Less */ in do_mathemu()
283 case 4: if (XR == 1) IR = 1; break; /* Less */ in do_mathemu()
284 case 5: if (XR & 2) IR = 1; break; /* Unordered or Greater */ in do_mathemu()
285 case 6: if (XR == 2) IR = 1; break; /* Greater */ in do_mathemu()
286 case 7: if (XR == 3) IR = 1; break; /* Unordered */ in do_mathemu()
[all …]
Dmath_32.c289 int IR; in do_one_mathemu() local
456 case FSTOI: FP_TO_INT_S (IR, SB, 32, 1); break; in do_one_mathemu()
457 case FDTOI: FP_TO_INT_D (IR, DB, 32, 1); break; in do_one_mathemu()
458 case FQTOI: FP_TO_INT_Q (IR, QB, 32, 1); break; in do_one_mathemu()
460 case FITOS: IR = rs2->s; FP_FROM_INT_S (SR, IR, 32, int); break; in do_one_mathemu()
461 case FITOD: IR = rs2->s; FP_FROM_INT_D (DR, IR, 32, int); break; in do_one_mathemu()
462 case FITOQ: IR = rs2->s; FP_FROM_INT_Q (QR, IR, 32, int); break; in do_one_mathemu()
473 FP_CMP_S(IR, SB, SA, 3); in do_one_mathemu()
474 if (IR == 3 && in do_one_mathemu()
482 FP_CMP_D(IR, DB, DA, 3); in do_one_mathemu()
[all …]
/linux-6.1.9/drivers/media/rc/
DKconfig9 standalone IR receivers/transmitters, and RF receivers.
12 if you don't need IR, as otherwise, you may not be able to
15 Say Y when you have a TV or an IR device.
26 syscall command BPF_PROG_ATTACH. This is supported for raw IR
29 These eBPF programs can be used to decode IR into scancodes, for
30 IR protocols not supported by the kernel decoders.
37 passes raw IR to and from userspace, which is needed for
38 IR transmitting (aka "blasting") and for the lirc daemon.
48 tristate "Enable IR raw decoder for the iMON protocol"
51 remote control and you would like to use it with a raw IR
[all …]
/linux-6.1.9/Documentation/userspace-api/media/rc/
Dlirc-dev-intro.rst10 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 …]
Drc-tables.rst10 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 …]
Dlirc-get-timeout.rst15 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
Drc-protos.rst9 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
186 and the command the higher 8 bits; this is reversed from IR order.
285 A plain nec IR message has 16 bits; the high 8 bits are the address
399 (40ms) space between the normal and inverted values, and some IR receivers
415 This is not an IR protocol, this is a protocol over CEC. The CEC
Dlirc-set-send-carrier.rst13 LIRC_SET_SEND_CARRIER - Set send carrier used to modulate IR TX.
34 Set send carrier used to modulate IR PWM pulses and spaces.
Dlirc-read.rst48 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>`
Dlirc-set-rec-carrier.rst13 LIRC_SET_REC_CARRIER - Set carrier used to modulate IR receive.
34 Set receive carrier used to modulate IR PWM pulses and spaces.
Dlirc-set-rec-carrier-range.rst14 IR receive.
36 by the IR receiver.
Drc-intro.rst19 device, as the IR receiver (and/or transmitter) can be used in
20 conjunction with a wide variety of different IR remotes.
Dlirc-set-send-duty-cycle.rst14 IR transmit.
36 Get/set the duty cycle of the carrier signal for IR transmit.
Dlirc-set-rec-timeout.rst14 LIRC_GET_REC_TIMEOUT/LIRC_SET_REC_TIMEOUT - Get/set the integer value for IR inactivity timeout.
39 Get and set the integer value for IR inactivity timeout.
/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-bus-iio-light-isl2901816 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
/linux-6.1.9/Documentation/driver-api/media/
Drc-core.rst26 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
/linux-6.1.9/Documentation/devicetree/bindings/media/
Dmtk-cir.txt1 Device-Tree bindings for Mediatek consumer IR controller
13 - interrupts : should contain IR IRQ number;
14 - reg : should contain IO map address for IR.
Damlogic,meson-ir-tx.yaml8 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.
/linux-6.1.9/drivers/media/rc/img-ir/
DKconfig3 tristate "ImgTec IR Decoder"
15 Say Y here to enable the raw mode driver which passes raw IR signal
16 changes to the IR raw decoders for software decoding. This is much
25 Say Y here to enable the hardware decode driver which decodes the IR
28 and allows an IR scancode to be used as a wake event.
/linux-6.1.9/arch/powerpc/math-emu/
Dmath_efp.c180 int IR, cmp; in do_spe_mathemu() local
333 FP_CMP_S(IR, SA, SB, 3); in do_spe_mathemu()
334 if (IR == 3 && (FP_ISSIGNAN_S(SA) || FP_ISSIGNAN_S(SB))) in do_spe_mathemu()
336 if (IR == cmp) { in do_spe_mathemu()
337 IR = 0x4; in do_spe_mathemu()
339 IR = 0; in do_spe_mathemu()
476 FP_CMP_D(IR, DA, DB, 3); in do_spe_mathemu()
477 if (IR == 3 && (FP_ISSIGNAN_D(DA) || FP_ISSIGNAN_D(DB))) in do_spe_mathemu()
479 if (IR == cmp) { in do_spe_mathemu()
480 IR = 0x4; in do_spe_mathemu()
[all …]
/linux-6.1.9/Documentation/driver-api/media/drivers/
Dcx88-devel.rst52 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
/linux-6.1.9/arch/arm64/boot/dts/amd/
Damd-seattle-xgbe-b.dtsi41 <0 0xe1250000 0 0x00060>, /* SERDES IR 1/2 */
42 <0 0xe12500f8 0 0x00004>; /* SERDES IR 2/2 */
67 <0 0xe1250080 0 0x00060>, /* SERDES IR 1/2 */
68 <0 0xe12500fc 0 0x00004>; /* SERDES IR 2/2 */
/linux-6.1.9/Documentation/devicetree/bindings/leds/irled/
Dgpio-ir-tx.txt1 Device tree bindings for IR LED connected through gpio pin which is used as
6 - gpios : Should specify the IR LED GPIO, see "gpios property" in
Dspi-ir-led.txt1 Device tree bindings for IR LED connected through SPI bus which is used as
4 The IR LED switch is connected to the MOSI line of the SPI device and the data
/linux-6.1.9/Documentation/admin-guide/media/
Dremote-controller.rst13 them have a microprocessor that receives the IR carriers, convert into
26 protocols it supports, enable in-kernel support for IR decoder or
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

1234