Searched refs:FOURCC (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/drivers/soc/apple/ |
| H A D | rtkit-crashlog.c | 8 #define FOURCC(a, b, c, d) \ macro
11 #define APPLE_RTKIT_CRASHLOG_HEADER FOURCC('C', 'L', 'H', 'E')
12 #define APPLE_RTKIT_CRASHLOG_STR FOURCC('C', 's', 't', 'r')
13 #define APPLE_RTKIT_CRASHLOG_VERSION FOURCC('C', 'v', 'e', 'r')
14 #define APPLE_RTKIT_CRASHLOG_MBOX FOURCC('C', 'm', 'b', 'x')
15 #define APPLE_RTKIT_CRASHLOG_TIME FOURCC('C', 't', 'i', 'm')
16 #define APPLE_RTKIT_CRASHLOG_REGS FOURCC('C', 'r', 'g', '8')
|
| /openbmc/linux/Documentation/fb/ |
| H A D | api.rst | 38 The driver supports the four character code (FOURCC) based format setting API.
39 When supported, formats are configured using a FOURCC instead of manually
88 Macropixels are stored in memory as described by the format FOURCC identifier
141 Pixels are encoded and interpreted as described by the format FOURCC
192 /* >1 = FOURCC */
218 __u32 colorspace; /* colorspace for FOURCC-based modes */
235 legacy API and the FOURCC-based API.
281 The FOURCC-based API replaces format descriptions by four character codes
282 (FOURCC). FOURCCs are abstract identifiers that uniquely define a format
287 Drivers that support the FOURCC-based API report this capability by setting
[all …]
|
| /openbmc/linux/drivers/staging/media/tegra-video/ |
| H A D | tegra20.c | 574 #define TEGRA20_VIDEO_FMT(MBUS_CODE, BPP, FOURCC) \ argument
578 .fourcc = V4L2_PIX_FMT_##FOURCC, \
|
| H A D | tegra210.c | 761 FORMAT, FOURCC) \ argument
768 V4L2_PIX_FMT_##FOURCC, \
|