| /kernel/linux/linux-5.10/scripts/dtc/ |
| D | yamltree.c | 32 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()
|
| 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 | 167 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()
|
| 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 | 451 struct marker *m = prop->val.markers; in check_duplicate_label_node()
480 m = prop->val.markers; in check_phandle_prop()
586 struct marker *m = prop->val.markers; in fixup_phandle_references()
621 struct marker *m = prop->val.markers; in fixup_path_references()
1399 if (prop->val.markers) { in check_property_phandle_args()
1400 struct marker *m = prop->val.markers; in check_property_phandle_args()
|
| D | dtc.h | 116 struct marker *markers; member
|
| D | flattree.c | 153 struct marker *m = d.markers; in asm_emit_data()
|
| /kernel/linux/linux-5.10/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.
83 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:
|
| /kernel/linux/linux-5.10/arch/riscv/mm/ |
| D | ptdump.c | 56 const struct addr_marker *markers; member
82 .markers = address_markers,
96 .markers = efi_addr_markers,
283 .marker = pinfo->markers, in ptdump_walk()
|
| /kernel/linux/linux-5.10/scripts/ |
| 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()
|
| /kernel/linux/linux-5.10/arch/arm64/include/asm/ |
| D | ptdump.h | 20 const struct addr_marker *markers; member
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | ptdump.h | 18 const struct addr_marker *markers; member
|
| /kernel/linux/linux-5.10/drivers/staging/media/hantro/ |
| D | TODO | 13 This might need to use extra JPEG markers for padding reasons.
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/ |
| D | arm-runtime.c | 33 .markers = (struct addr_marker[]){
|
| /kernel/linux/linux-5.10/arch/arm64/mm/ |
| D | ptdump.c | 326 .marker = info->markers, in ptdump_walk()
351 .markers = address_markers,
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 211 # V4L2 JPEG markers
212 replace define V4L2_JPEG_MARKER_DHT jpeg-markers
213 replace define V4L2_JPEG_MARKER_DQT jpeg-markers
214 replace define V4L2_JPEG_MARKER_DRI jpeg-markers
215 replace define V4L2_JPEG_MARKER_COM jpeg-markers
216 replace define V4L2_JPEG_MARKER_APP jpeg-markers
|
| /kernel/linux/linux-5.10/ |
| D | .gitignore | 66 /Module.markers
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | dump.c | 411 .marker = info->markers, in ptdump_walk_pgd()
438 .markers = address_markers,
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | dontdiff | 75 Module.markers
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | s2ram.rst | 24 time-consuming - having to insert TRACE_RESUME() markers into the device
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| D | Kconfig | 101 explicit rcu_read_lock_trace() read-side markers, and allows
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | coding-style.rst | 1027 indicated with special markers. For example, emacs interprets lines marked
1044 Vim interprets markers that look like this:
1052 includes markers for indentation and mode configuration. People may use their
|
| /kernel/linux/linux-5.10/Documentation/input/ |
| D | event-codes.rst | 36 - Used as markers to separate events. Events may be separated in time or in
|