drivers/dma-buf/sync_debug.h

File Facts

System

Linux kernel

Corpus path

drivers/dma-buf/sync_debug.h

Extension

.h

Size

1847 bytes

Lines

73

Domain

Driver Families

Bucket

drivers/dma-buf

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/list.h
• linux/rbtree.h
• linux/spinlock.h
• linux/dma-fence.h
• linux/sync_file.h
• uapi/linux/sync_file.h

Detected Declarations

• struct sync_timeline
• struct sync_pt

Annotated Snippet

extern const struct file_operations sw_sync_debugfs_fops;

void sync_timeline_debug_add(struct sync_timeline *obj);
void sync_timeline_debug_remove(struct sync_timeline *obj);

#endif /* _LINUX_SYNC_H */

Annotation

• Immediate include surface: `linux/list.h`, `linux/rbtree.h`, `linux/spinlock.h`, `linux/dma-fence.h`, `linux/sync_file.h`, `uapi/linux/sync_file.h`.
• Detected declarations: `struct sync_timeline`, `struct sync_pt`.
• Atlas domain: Driver Families / drivers/dma-buf.
• Implementation status: pattern implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.