| /Linux-v6.1/scripts/dtc/ |
| 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()
|
| 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()
|
| 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()
|
| 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()
|
| 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()
|
| D | dtc.h | 137 struct marker *markers; member
|
| D | flattree.c | 154 struct marker *m = d.markers; in asm_emit_data()
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| 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
|
| D | vidioc-g-jpegcomp.rst | 40 markers control.
89 - See :ref:`jpeg-markers`. Deprecated. If
96 .. _jpeg-markers:
|
| /Linux-v6.1/arch/riscv/mm/ |
| 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-v6.1/scripts/ |
| D | kallsyms.c | 417 unsigned int *markers; in write_src() local
486 markers = malloc(sizeof(unsigned int) * ((table_cnt + 255) / 256)); in write_src()
487 if (!markers) { in write_src()
497 markers[i >> 8] = off; in write_src()
533 printf("\t.long\t%u\n", markers[i]); in write_src()
536 free(markers); in write_src()
|
| /Linux-v6.1/arch/arm/include/asm/ |
| D | ptdump.h | 18 const struct addr_marker *markers; member
|
| /Linux-v6.1/arch/arm64/include/asm/ |
| D | ptdump.h | 20 const struct addr_marker *markers; member
|
| /Linux-v6.1/arch/arm64/mm/ |
| D | ptdump.c | 318 .marker = info->markers, in ptdump_walk()
344 .markers = address_markers,
|
| /Linux-v6.1/drivers/firmware/efi/ |
| D | arm-runtime.c | 33 .markers = (struct addr_marker[]){
|
| /Linux-v6.1/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 229 # V4L2 JPEG markers
230 replace define V4L2_JPEG_MARKER_DHT jpeg-markers
231 replace define V4L2_JPEG_MARKER_DQT jpeg-markers
232 replace define V4L2_JPEG_MARKER_DRI jpeg-markers
233 replace define V4L2_JPEG_MARKER_COM jpeg-markers
234 replace define V4L2_JPEG_MARKER_APP jpeg-markers
|
| /Linux-v6.1/arch/arm/mm/ |
| D | dump.c | 419 .marker = info->markers, in ptdump_walk_pgd()
449 .markers = address_markers,
|
| /Linux-v6.1/ |
| D | .gitignore | 68 /Module.markers
|
| /Linux-v6.1/Documentation/ |
| D | dontdiff | 75 Module.markers
|
| /Linux-v6.1/Documentation/trace/ |
| 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-v6.1/Documentation/power/ |
| D | s2ram.rst | 24 time-consuming - having to insert TRACE_RESUME() markers into the device
|
| /Linux-v6.1/tools/memory-model/Documentation/ |
| 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-v6.1/kernel/rcu/ |
| D | Kconfig | 122 explicit rcu_read_lock_trace() read-side markers, and allows
|
| /Linux-v6.1/Documentation/process/ |
| D | coding-style.rst | 1078 indicated with special markers. For example, emacs interprets lines marked
1095 Vim interprets markers that look like this:
1103 includes markers for indentation and mode configuration. People may use their
|
| /Linux-v6.1/Documentation/dev-tools/ |
| D | checkpatch.rst | 858 It is possible to use section markers on variables in a way
1197 Since linux moved to git, the CVS markers are no longer used.
|
