Home
last modified time | relevance | path

Searched full:markers (Results 1 – 25 of 104) sorted by relevance

12345

/Linux-v5.4/drivers/media/platform/s5p-jpeg/
Djpeg-core.h39 /* a selection of JPEG markers */
172 * s5p_jpeg_marker - collection of markers from jpeg header
173 * @marker: markers' positions relative to the buffer beginning
174 * @len: markers' payload lengths (without length field)
175 * @n: number of markers in collection
189 * @dht: DHT markers' positions relative to the buffer beginning
190 * @dqt: DQT markers' positions relative to the buffer beginning
/Linux-v5.4/Documentation/media/uapi/v4l/
Dext-ctrls-jpeg.rst63 markers (m = 0..7). The purpose of these markers is to additionally
69 markers will not be inserted.
90 Specify which JPEG markers are included in compressed stream. This
Dvidioc-g-jpegcomp.rst47 markers control.
97 - See :ref:`jpeg-markers`. Deprecated. If
105 .. _jpeg-markers:
107 .. flat-table:: JPEG Markers Flags
/Linux-v5.4/scripts/dtc/
Ddata.c12 m = d.markers; in data_free()
123 /* Adjust all markers after the one we're inserting at */ in data_insert_at_marker()
132 struct marker **mp = &d.markers; in data_append_markers()
144 struct marker *m2 = d2.markers; in data_merge()
152 d2.markers = NULL; /* So data_free() doesn't clobber them */ in data_merge()
Dyamltree.c32 static void yaml_propval_int(yaml_emitter_t *emitter, struct marker *markers, char *data, int len, … in yaml_propval_int() argument
36 int off, start_offset = markers->offset; in yaml_propval_int()
66 m = markers; in yaml_propval_int()
116 struct marker *m = prop->val.markers; in yaml_propval()
135 die("No markers present in property '%s' value\n", prop->name); in yaml_propval()
Dtreesource.c167 struct marker *m = prop->val.markers; in guess_value_type()
199 struct marker *m = prop->val.markers; in write_propval()
222 dummy_marker.next = prop->val.markers; in write_propval()
Dlivetree.c484 m = p->val.markers; in get_marker_label()
872 m = prop->val.markers; in any_fixup_tree()
918 m = prop->val.markers; in generate_fixups_tree_internal()
937 m = prop->val.markers; in any_local_fixup_tree()
999 m = prop->val.markers; in generate_local_fixups_tree_internal()
/Linux-v5.4/drivers/staging/fwserial/
Ddma_fifo.h25 * then the in and out markers are re-aligned to the next cache line.
33 * guard area, but the in and out FIFO markers are wrapped when DMA is pended.
53 struct list_head pending; /* fifo markers for outstanding dma */
/Linux-v5.4/Documentation/media/
Dvideodev2.h.rst.exceptions200 # V4L2 JPEG markers
201 replace define V4L2_JPEG_MARKER_DHT jpeg-markers
202 replace define V4L2_JPEG_MARKER_DQT jpeg-markers
203 replace define V4L2_JPEG_MARKER_DRI jpeg-markers
204 replace define V4L2_JPEG_MARKER_COM jpeg-markers
205 replace define V4L2_JPEG_MARKER_APP jpeg-markers
/Linux-v5.4/scripts/
Dkallsyms.c334 unsigned int *markers; in write_src() local
412 /* table of offset markers, that give the offset in the compressed stream in write_src()
414 markers = malloc(sizeof(unsigned int) * ((table_cnt + 255) / 256)); in write_src()
415 if (!markers) { in write_src()
425 markers[i >> 8] = off; in write_src()
438 printf("\t.long\t%u\n", markers[i]); in write_src()
441 free(markers); in write_src()
/Linux-v5.4/Documentation/devicetree/bindings/mtd/
Dnand-controller.yaml82 find Bad Block Markers (BBM). These markers will help to
/Linux-v5.4/drivers/media/pci/cx18/
Dcx18-vbi.c34 0x44, 0x00, 0x0c, 0x66, 0x24, 0x01, /* SCR, SCR Ext, markers */ in copy_vbi_data()
35 0x01, 0xd1, 0xd3, /* Mux Rate, markers */ in copy_vbi_data()
41 0x21, 0x00, 0x5d, 0x63, 0xa7, /* PTS, markers */ in copy_vbi_data()
/Linux-v5.4/drivers/staging/media/hantro/
DTODO13 This might need to use extra JPEG markers for padding reasons.
/Linux-v5.4/arch/arm/include/asm/
Dptdump.h18 const struct addr_marker *markers; member
/Linux-v5.4/arch/arm64/include/asm/
Dptdump.h20 const struct addr_marker *markers; member
/Linux-v5.4/drivers/mtd/nand/raw/
Dnand_esmt.c41 * with the factory bad block markers in the first or last page in esmt_nand_init()
Dnand_amd.c41 * the bad block markers can be in the first, second or last in amd_nand_init()
/Linux-v5.4/Documentation/trace/
Dmmiotrace.rst70 During tracing you can place comments (markers) into the trace by
73 which action. It is recommended to place descriptive markers about what you
/Linux-v5.4/drivers/char/
Ddtlk.c28 read from the TTS port, and index markers (which mark the progress
30 DoubleTalk PC implement index markers. Both the TTS and LPC ports
44 "read" gets index markers from the LPC port. If the device does
45 not implement index markers, the read will fail with error EINVAL.
/Linux-v5.4/include/uapi/linux/
Datm_nicstar.h28 /* set buffer level markers */
/Linux-v5.4/drivers/infiniband/hw/i40iw/
Di40iw_cm.h78 IETF_MPA_FLAGS_MARKERS = 0x80, /* receive Markers */
79 IETF_MPA_FLAGS_CRC = 0x40, /* receive Markers */
/Linux-v5.4/
D.gitignore62 /Module.markers
/Linux-v5.4/include/linux/
Dinit.h64 * The following markers are used for the cases where the reference to
71 * The markers follow same syntax rules as __init / __initdata.
Dmmiotrace.h52 /* For anyone to insert markers. Remember trailing newline. */
/Linux-v5.4/arch/x86/mm/
Ddump_pagetables.c47 /* Address space markers hints */
324 * We print markers for special areas of address space, in note_page()
607 * Various markers are not compile-time constants, so assign them in pt_dump_init()

12345