Searched full:codes (Results 1 – 25 of 350) sorted by relevance
12345678910>>...14
| /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
51 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | lirc-set-send-carrier.rst | 40 appropriately. The generic error codes are described at the
41 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 3 bcachefs private error codes
7 codes (-EINVAL, -EBUSY, etc.). Instead, we define private error codes as needed
11 direct uses of standard error codes you see in the source code are simply old
14 Private error codes may subtype another error code, this allows for grouping of
23 Do not reuse error codes! Generally speaking, a private error code should only
27 Try to give error codes names that are as reasonably descriptive of the error
29 where the error was generated; good names for error codes mean much more
|
| /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 …]
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 2 I2C/SMBUS Fault Codes
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
|
| /Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 6 GPIO Error Codes
13 .. flat-table:: Common GPIO error codes
73 #. This list is not exhaustive; ioctls may return other error codes.
78 #. Request-specific error codes are listed in the individual
|
| D | gpio-get-chipinfo-ioctl.rst | 41 Common error codes are described in error-codes.rst.
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_audio.rst | 501 appropriately. The generic error codes are described at the
502 :ref:`Generic Error Codes <gen-errors>` chapter.
552 appropriately. The generic error codes are described at the
553 :ref:`Generic Error Codes <gen-errors>` chapter.
605 appropriately. The generic error codes are described at the
606 :ref:`Generic Error Codes <gen-errors>` chapter.
657 appropriately. The generic error codes are described at the
658 :ref:`Generic Error Codes <gen-errors>` chapter.
720 appropriately. The generic error codes are described at the
721 :ref:`Generic Error Codes <gen-errors>` chapter.
[all …]
|
| D | legacy_dvb_video.rst | 875 appropriately. The generic error codes are described at the
876 :ref:`Generic Error Codes <gen-errors>` chapter.
930 appropriately. The generic error codes are described at the
931 :ref:`Generic Error Codes <gen-errors>` chapter.
990 appropriately. The generic error codes are described at the
991 :ref:`Generic Error Codes <gen-errors>` chapter.
1045 appropriately. The generic error codes are described at the
1046 :ref:`Generic Error Codes <gen-errors>` chapter.
1114 appropriately. The generic error codes are described at the
1115 :ref:`Generic Error Codes <gen-errors>` chapter.
[all …]
|
| D | ca-reset.rst | 42 Generic error codes are described at the
43 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | dmx-stop.rst | 43 The generic error codes are described at the
44 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | ca-get-descr-info.rst | 42 appropriately. The generic error codes are described at the
43 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | ca-get-cap.rst | 45 The generic error codes are described at the
46 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | ca-set-descr.rst | 45 Generic error codes are described at the
46 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | ca-fclose.rst | 39 Generic error codes are described at the
40 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | dmx-add-pid.rst | 46 Generic error codes are described at the
47 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | ca-get-msg.rst | 49 Generic error codes are described at the
50 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| D | dmx-fclose.rst | 41 The generic error codes are described at the
42 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 6 Generic Error Codes
14 .. flat-table:: Generic error codes
88 #. This list is not exhaustive; ioctls may return other error codes.
93 #. Request-specific error codes are listed in the individual
|
| /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`
80 Error codes returned by ``in urb->status`` or in ``iso_frame_desc[n].status`` (for ISO)
97 may report more status codes.
180 Error codes like ``-EPROTO``, ``-EILSEQ`` and ``-EOVERFLOW`` normally
186 This is also one of several codes that different kinds of host
193 Error codes returned by usbcore-functions
196 .. note:: expect also other submit and transfer status codes
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-func-ioctl.rst | 56 appropriately. The generic error codes are described at the
57 :ref:`Generic Error Codes <gen-errors>` chapter.
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
57 :ref:`Generic Error Codes <gen-errors>` chapter.
59 Request-specific error codes are listed in the individual requests
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-ioctl.rst | 56 appropriately. The generic error codes are described at the
57 :ref:`Generic Error Codes <gen-errors>` chapter.
59 Request-specific error codes are listed in the individual requests
|
| /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
|
12345678910>>...14