| /Linux-v5.4/Documentation/media/uapi/rc/ |
| D | keytable.c.rst | 40 void prtcode (int *codes)
45 if (p->value == (unsigned)codes[1]) {
46 printf("scancode 0x%04x = %s (0x%02x)\\n", codes[0], p->name, codes[1]);
51 if (isprint (codes[1]))
52 printf("scancode %d = '%c' (0x%02x)\\n", codes[0], codes[1], codes[1]);
54 printf("scancode %d = 0x%02x\\n", codes[0], codes[1]);
73 int codes[2];
98 codes [0] = (unsigned) strtol(argv[2], NULL, 0);
99 codes [1] = (unsigned) value;
101 if(ioctl(fd, EVIOCSKEYCODE, codes))
[all …]
|
| D | lirc-set-transmitter-mask.rst | 19 LIRC_SET_TRANSMITTER_MASK - Enables send codes on a given set of transmitters
43 send IR codes.
57 appropriately. The generic error codes are described at the
|
| /Linux-v5.4/drivers/input/keyboard/ |
| D | dlink-dir685-touchkeys.c | 24 u16 codes[7]; member
30 const int num_bits = min_t(int, ARRAY_SIZE(tk->codes), 16); in dir685_tk_irq_thread()
52 input_report_key(tk->input, tk->codes[i], test_bit(i, &key)); in dir685_tk_irq_thread()
83 tk->input->keycodemax = ARRAY_SIZE(tk->codes); in dir685_tk_probe()
84 tk->input->keycode = tk->codes; in dir685_tk_probe()
85 tk->codes[0] = KEY_UP; in dir685_tk_probe()
86 tk->codes[1] = KEY_DOWN; in dir685_tk_probe()
87 tk->codes[2] = KEY_LEFT; in dir685_tk_probe()
88 tk->codes[3] = KEY_RIGHT; in dir685_tk_probe()
89 tk->codes[4] = KEY_ENTER; in dir685_tk_probe()
[all …]
|
| D | ipaq-micro-keys.c | 26 u16 *codes; member
50 input_report_key(keys->input, keys->codes[key], down); in micro_key_receive()
105 keys->codes = devm_kmemdup(&pdev->dev, micro_keycodes, in micro_key_probe()
108 keys->input->keycode = keys->codes; in micro_key_probe()
|
| /Linux-v5.4/drivers/staging/media/imx/ |
| D | imx-media-utils.c | 20 .codes = {
28 .codes = {
74 .codes = {MEDIA_BUS_FMT_RGB565_2X8_LE},
80 .codes = {
88 .codes = {MEDIA_BUS_FMT_ARGB8888_1X32},
96 .codes = {MEDIA_BUS_FMT_SBGGR8_1X8},
102 .codes = {MEDIA_BUS_FMT_SGBRG8_1X8},
108 .codes = {MEDIA_BUS_FMT_SGRBG8_1X8},
114 .codes = {MEDIA_BUS_FMT_SRGGB8_1X8},
120 .codes = {
[all …]
|
| /Linux-v5.4/drivers/media/i2c/ |
| D | ir-kbd-i2c.c | 369 u8 codes[61]; member
502 u8 codes[174]; in zilog_ir_format() local
510 if (c >= ARRAY_SIZE(codes) - 1) { in zilog_ir_format()
533 codes[c++] = (p << 4) | s; in zilog_ir_format()
553 codes[c++] = (p << 4) | s; in zilog_ir_format()
565 if (!memcmp(&codes[c - rep * 3], &codes[c - rep * 2], rep) && in zilog_ir_format()
566 !cmp_no_trail(&codes[c - rep], &codes[c - rep * 2], rep)) { in zilog_ir_format()
576 if (leading >= ARRAY_SIZE(code_block->codes) - 3 - rep) { in zilog_ir_format()
582 copy_codes(code_block->codes, codes, leading); in zilog_ir_format()
583 code_block->codes[leading] = 0x82; in zilog_ir_format()
[all …]
|
| /Linux-v5.4/Documentation/input/ |
| D | event-codes.rst | 1 .. _input-event-codes:
4 Input event codes
8 The input protocol uses a map of types and codes to express input device values
9 to userspace. This document describes the types and codes and how and when they
19 of event codes have changed. However, the state is maintained within the Linux
30 Event types are groupings of codes under a logical input construct. Each
31 type has a set of applicable codes to be used in generating events. See the
32 Codes section for details on valid codes for each type.
86 Event codes
89 Event codes define the precise type of event.
[all …]
|
| D | input_uapi.rst | 16 event-codes
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | error-codes.rst | 1 .. _usb-error-codes:
3 USB Error codes
8 This is the documentation of (hopefully) all possible error codes (and
17 Error codes returned by :c:func:`usb_submit_urb`
77 Error codes returned by ``in urb->status`` or in ``iso_frame_desc[n].status`` (for ISO)
94 may report more status codes.
177 Error codes like ``-EPROTO``, ``-EILSEQ`` and ``-EOVERFLOW`` normally
183 This is also one of several codes that different kinds of host
190 Error codes returned by usbcore-functions
193 .. note:: expect also other submit and transfer status codes
|
| D | index.rst | 17 error-codes
|
| /Linux-v5.4/Documentation/i2c/ |
| D | fault-codes.rst | 6 codes in the I2C/SMBus stack.
21 In short, your I2C driver code may need to know these codes in order
26 I2C and SMBus fault codes
34 codes that may be returned, and other cases where these codes should
35 be returned. However, drivers should not return other codes for these
38 Also, codes returned by adapter probe methods follow rules which are
|
| D | index.rst | 12 fault-codes
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | v4l-with-ir.rst | 13 pulse/space sequences and then to scan codes, returning such codes to
26 switch the protocol and to test the reception of scan codes;
61 linux input layer (via event device). It also supports receiving IR codes
|
| /Linux-v5.4/lib/zlib_inflate/ |
| D | inftrees.c | 23 int zlib_inflate_table(codetype type, unsigned short *lens, unsigned codes, in zlib_inflate_table() argument
95 for (sym = 0; sym < codes; sym++) in zlib_inflate_table()
132 for (sym = 0; sym < codes; sym++) in zlib_inflate_table()
|
| D | inftrees.h | 57 unsigned codes, code **table,
|
| /Linux-v5.4/drivers/media/platform/vsp1/ |
| D | vsp1_entity.c | 244 const unsigned int *codes, unsigned int ncodes) in vsp1_subdev_enum_mbus_code() argument
252 code->code = codes[code->index]; in vsp1_subdev_enum_mbus_code()
358 const unsigned int *codes, unsigned int ncodes, in vsp1_subdev_set_pad_format() argument
390 if (fmt->format.code == codes[i]) in vsp1_subdev_set_pad_format()
394 format->code = i < ncodes ? codes[i] : codes[0]; in vsp1_subdev_set_pad_format()
|
| D | vsp1_entity.h | 181 const unsigned int *codes, unsigned int ncodes,
187 const unsigned int *codes, unsigned int ncodes);
|
| D | vsp1_rwpf.c | 34 static const unsigned int codes[] = { in vsp1_rwpf_enum_mbus_code() local
40 if (code->index >= ARRAY_SIZE(codes)) in vsp1_rwpf_enum_mbus_code()
43 code->code = codes[code->index]; in vsp1_rwpf_enum_mbus_code()
|
| /Linux-v5.4/Documentation/devicetree/bindings/input/ |
| D | qcom,pm8941-pwrkey.txt | 40 Use the linux event codes defined in
41 include/dt-bindings/input/linux-event-codes.h
|
| /Linux-v5.4/Documentation/devicetree/bindings/misc/ |
| D | xlnx,sd-fec.txt | 6 customer specified Quasi-cyclic (QC) codes. The Turbo decode functionality
7 principally covers codes used by LTE. The FEC Engine offers significant
25 - xlnx,sdfec-code : Should contain "ldpc" or "turbo" to describe the codes
|
| /Linux-v5.4/Documentation/media/uapi/ |
| D | gen-errors.rst | 21 .. flat-table:: Generic error codes
97 #. This list is not exhaustive; ioctls may return other error codes.
102 #. Request-specific error codes are listed in the individual
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 49 more acceptable exit codes for this command.
70 more acceptable exit codes for this command.
87 It's possible to include acceptable exit codes with the setup/teardown command
90 acceptable exit codes for the command.
|
| /Linux-v5.4/Documentation/media/uapi/mediactl/ |
| D | media-func-ioctl.rst | 67 appropriately. The generic error codes are described at the
70 Request-specific error codes are listed in the individual requests
|
| /Linux-v5.4/Documentation/media/uapi/cec/ |
| D | cec-func-ioctl.rst | 66 appropriately. The generic error codes are described at the
69 Request-specific error codes are listed in the individual requests
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | unicode.rst | 37 Note that although these codes are similar to ISO 2022, neither the
38 codes nor their uses match ISO 2022; Linux has two 8-bit codes (G0 and
39 G1), whereas ISO 2022 has four 7-bit codes (G0-G3).
185 wish to encode fictional scripts use these codes, in the interest of
|
