Home
last modified time | relevance | path

Searched refs:codes (Results 1 – 25 of 410) sorted by relevance

12345678910>>...17

/linux/Documentation/userspace-api/media/rc/
H A Dkeytable.c.rst33 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 …]
H A Dlirc-set-transmitter-mask.rst13 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
/linux/drivers/staging/media/imx/
H A Dimx-media-utils.c19 .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 …]
/linux/Documentation/driver-api/usb/
H A Derror-codes.rst1 .. _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
/linux/Documentation/i2c/
H A Dfault-codes.rst6 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
/linux/Documentation/userspace-api/gpio/
H A Dgpio-get-chipinfo-ioctl.rst41 Common error codes are described in error-codes.rst.
H A Derror-codes.rst13 .. 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
H A Dgpio-get-lineinfo-unwatch-ioctl.rst49 Common error codes are described in error-codes.rst.
H A Dgpio-v2-get-lineinfo-ioctl.rst50 Common error codes are described in error-codes.rst.
H A Dgpio-get-lineinfo-ioctl.rst54 Common error codes are described in error-codes.rst.
H A Dgpio-handle-set-line-values-ioctl.rst55 Common error codes are described in error-codes.rst.
H A Dgpio-v2-line-set-values-ioctl.rst54 Common error codes are described in error-codes.rst.
H A Dgpio-v2-line-get-values-ioctl.rst58 Common error codes are described in error-codes.rst.
H A Dgpio-v2-line-set-config-ioctl.rst61 Common error codes are described in error-codes.rst.
H A Dgpio-handle-set-config-ioctl.rst66 Common error codes are described in error-codes.rst.
H A Dgpio-handle-get-line-values-ioctl.rst63 Common error codes are described in error-codes.rst.
/linux/Documentation/admin-guide/media/
H A Dremote-controller.rst14 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
/linux/drivers/media/i2c/adv748x/
H A Dadv748x-csi2.c182 const unsigned int *codes = is_txa(tx) ? in adv748x_csi2_enum_mbus_code() local
207 code->code = codes[code->index]; in adv748x_csi2_enum_mbus_code()
214 const unsigned int *codes = is_txa(tx) ? in adv748x_csi2_is_fmt_supported() local
221 if (codes[i] == code) in adv748x_csi2_is_fmt_supported()
/linux/lib/zlib_inflate/
H A Dinftrees.c23 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()
/linux/Documentation/userspace-api/media/
H A Dgen-errors.rst14 .. 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
/linux/Documentation/userspace-api/media/dvb/
H A Dlegacy_dvb_video.rst875 appropriately. The generic error codes are described at the
930 appropriately. The generic error codes are described at the
990 appropriately. The generic error codes are described at the
1045 appropriately. The generic error codes are described at the
1114 appropriately. The generic error codes are described at the
1183 appropriately. The generic error codes are described at the
1242 appropriately. The generic error codes are described at the
1314 appropriately. The generic error codes are described at the
1390 appropriately. The generic error codes are described at the
1457 appropriately. The generic error codes are described at the
[all …]
/linux/Documentation/userspace-api/media/mediactl/
H A Dmedia-func-ioctl.rst56 appropriately. The generic error codes are described at the
59 Request-specific error codes are listed in the individual requests
H A Drequest-func-ioctl.rst56 appropriately. The generic error codes are described at the
59 Command-specific error codes are listed in the individual command
/linux/Documentation/userspace-api/media/cec/
H A Dcec-func-ioctl.rst56 appropriately. The generic error codes are described at the
59 Request-specific error codes are listed in the individual requests
/linux/tools/testing/selftests/tc-testing/creating-testcases/
H A DAddingTestCases.txt51 more acceptable exit codes for this command.
72 more acceptable exit codes for this command.
89 It's possible to include acceptable exit codes with the setup/teardown command
92 acceptable exit codes for the command.

12345678910>>...17