| /kernel/linux/linux-5.10/Documentation/userspace-api/media/rc/ |
| D | keytable.c.rst | 33 void prtcode (int *codes)
38 if (p->value == (unsigned)codes[1]) {
39 printf("scancode 0x%04x = %s (0x%02x)\\n", codes[0], p->name, codes[1]);
44 if (isprint (codes[1]))
45 printf("scancode %d = '%c' (0x%02x)\\n", codes[0], codes[1], codes[1]);
47 printf("scancode %d = 0x%02x\\n", codes[0], codes[1]);
66 int codes[2];
91 codes [0] = (unsigned) strtol(argv[2], NULL, 0);
92 codes [1] = (unsigned) value;
94 if(ioctl(fd, EVIOCSKEYCODE, codes))
[all …]
|
| D | lirc-set-transmitter-mask.rst | 13 LIRC_SET_TRANSMITTER_MASK - Enables send codes on a given set of transmitters
37 send IR codes.
50 appropriately. The generic error codes are described at the
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/drivers/staging/media/imx/ |
| D | imx-media-utils.c | 19 .codes = IMX_BUS_FMTS(
27 .codes = IMX_BUS_FMTS(
60 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_AYUV8_1X32),
68 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_RGB565_2X8_LE),
74 .codes = IMX_BUS_FMTS(
86 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_ARGB8888_1X32),
91 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_ARGB8888_1X32),
111 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_SBGGR8_1X8),
117 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_SGBRG8_1X8),
123 .codes = IMX_BUS_FMTS(MEDIA_BUS_FMT_SGRBG8_1X8),
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| D | imx219.c | 430 static const u32 codes[] = { variable
655 for (i = 0; i < ARRAY_SIZE(codes); i++) in imx219_get_format_code()
656 if (codes[i] == code) in imx219_get_format_code()
659 if (i >= ARRAY_SIZE(codes)) in imx219_get_format_code()
665 return codes[i]; in imx219_get_format_code()
808 if (code->index >= (ARRAY_SIZE(codes) / 4)) in imx219_enum_mbus_code()
811 code->code = imx219_get_format_code(imx219, codes[code->index * 4]); in imx219_enum_mbus_code()
901 for (i = 0; i < ARRAY_SIZE(codes); i++) in imx219_set_pad_format()
902 if (codes[i] == fmt->format.code) in imx219_set_pad_format()
904 if (i >= ARRAY_SIZE(codes)) in imx219_set_pad_format()
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | remote-controller.rst | 14 pulse/space sequences and then to scan codes, returning such codes to
27 switch the protocol and to test the reception of scan codes;
62 linux input layer (via event device). It also supports receiving IR codes
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/ |
| D | gen-errors.rst | 14 .. flat-table:: Generic error codes
90 #. This list is not exhaustive; ioctls may return other error codes.
95 #. Request-specific error codes are listed in the individual
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | dell-smm-hwmon.rst | 61 If ``pwm1_enable`` is not available, then it means that SMM codes for
63 for your hardware. It is possible that codes that work for other
65 new codes.
80 probe the BIOS on your machine and discover the appropriate codes.
84 Again, when you find new codes, we'd be happy to have your patches!
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | request-func-ioctl.rst | 56 appropriately. The generic error codes are described at the
59 Command-specific error codes are listed in the individual command
|
| D | media-func-ioctl.rst | 56 appropriately. The generic error codes are described at the
59 Request-specific error codes are listed in the individual requests
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/cec/ |
| D | cec-func-ioctl.rst | 56 appropriately. The generic error codes are described at the
59 Request-specific error codes are listed in the individual requests
|
| /kernel/linux/linux-5.10/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.
|