/linux/scripts/dtc/ |
A D | yamltree.c | 32 static void yaml_propval_int(yaml_emitter_t *emitter, struct marker *markers, in yaml_propval_int() argument 67 m = markers; in yaml_propval_int() 117 struct marker *m = prop->val.markers; in yaml_propval() 118 struct marker *markers = prop->val.markers; in yaml_propval() local 156 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 2); in yaml_propval() 159 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 4); in yaml_propval() 162 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 8); in yaml_propval() 168 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 1); in yaml_propval()
|
A D | data.c | 12 m = d.markers; in data_free() 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()
|
A D | treesource.c | 146 struct marker *m = prop->val.markers; in guess_value_type() 178 struct marker *m = prop->val.markers; in write_propval() 201 dummy_marker.next = prop->val.markers; in write_propval() 227 m_phandle = prop->val.markers; in write_propval()
|
A D | livetree.c | 484 m = p->val.markers; in get_marker_label() 871 m = prop->val.markers; in any_fixup_tree() 917 m = prop->val.markers; in generate_fixups_tree_internal() 936 m = prop->val.markers; in any_local_fixup_tree() 998 m = prop->val.markers; in generate_local_fixups_tree_internal()
|
A D | checks.c | 474 struct marker *m = prop->val.markers; in check_duplicate_label_node() 503 m = prop->val.markers; in check_phandle_prop() 609 struct marker *m = prop->val.markers; in fixup_phandle_references() 644 struct marker *m = prop->val.markers; in fixup_path_references() 1420 if (prop->val.markers) { in check_property_phandle_args() 1421 struct marker *m = prop->val.markers; in check_property_phandle_args()
|
A D | dtc.h | 137 struct marker *markers; member
|
A D | flattree.c | 154 struct marker *m = d.markers; in asm_emit_data()
|
/linux/Documentation/userspace-api/media/v4l/ |
A D | ext-ctrls-jpeg.rst | 56 markers (m = 0..7). The purpose of these markers is to additionally 62 markers will not be inserted. 82 Specify which JPEG markers are included in compressed stream. This
|
A D | vidioc-g-jpegcomp.rst | 40 markers control. 89 - See :ref:`jpeg-markers`. Deprecated. If 96 .. _jpeg-markers:
|
/linux/scripts/ |
A D | kallsyms.c | 391 unsigned int *markers; in write_src() local 460 markers = malloc(sizeof(unsigned int) * ((table_cnt + 255) / 256)); in write_src() 461 if (!markers) { in write_src() 471 markers[i >> 8] = off; in write_src() 484 printf("\t.long\t%u\n", markers[i]); in write_src() 487 free(markers); in write_src()
|
/linux/arch/riscv/mm/ |
A D | ptdump.c | 56 const struct addr_marker *markers; member 109 .markers = address_markers, 123 .markers = efi_addr_markers, 310 .marker = pinfo->markers, in ptdump_walk()
|
/linux/arch/arm/include/asm/ |
A D | ptdump.h | 18 const struct addr_marker *markers; member
|
/linux/arch/arm64/include/asm/ |
A D | ptdump.h | 20 const struct addr_marker *markers; member
|
/linux/drivers/staging/media/hantro/ |
A D | TODO | 13 This might need to use extra JPEG markers for padding reasons.
|
/linux/arch/arm64/mm/ |
A D | ptdump.c | 320 .marker = info->markers, in ptdump_walk() 346 .markers = address_markers,
|
/linux/drivers/firmware/efi/ |
A D | arm-runtime.c | 33 .markers = (struct addr_marker[]){
|
/linux/Documentation/userspace-api/media/ |
A D | videodev2.h.rst.exceptions | 219 # V4L2 JPEG markers 220 replace define V4L2_JPEG_MARKER_DHT jpeg-markers 221 replace define V4L2_JPEG_MARKER_DQT jpeg-markers 222 replace define V4L2_JPEG_MARKER_DRI jpeg-markers 223 replace define V4L2_JPEG_MARKER_COM jpeg-markers 224 replace define V4L2_JPEG_MARKER_APP jpeg-markers
|
/linux/arch/arm/mm/ |
A D | dump.c | 415 .marker = info->markers, in ptdump_walk_pgd() 445 .markers = address_markers,
|
/linux/ |
A D | .gitignore | 65 /Module.markers
|
/linux/Documentation/trace/ |
A D | mmiotrace.rst | 70 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/Documentation/ |
A D | dontdiff | 75 Module.markers
|
/linux/Documentation/power/ |
A D | s2ram.rst | 24 time-consuming - having to insert TRACE_RESUME() markers into the device
|
/linux/Documentation/devicetree/bindings/mtd/ |
A D | nand-controller.yaml | 112 find Bad Block Markers (BBM). These markers will help to
|
/linux/tools/memory-model/Documentation/ |
A D | ordering.txt | 374 This category includes read-side markers such as rcu_read_lock() 378 Compared to locking primitives and RMW atomic operations, markers 381 For example, the rcu_read_lock() and rcu_read_unlock() markers interact
|
/linux/kernel/rcu/ |
A D | Kconfig | 101 explicit rcu_read_lock_trace() read-side markers, and allows
|