drivers/gpu/drm/msm/msm_syncobj.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/msm/msm_syncobj.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/msm/msm_syncobj.h- Extension
.h- Size
- 1028 bytes
- Lines
- 38
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: implementation source
- Status
- source 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 or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
drm/drm_device.hdrm/drm_syncobj.hdrm/gpu_scheduler.h
Detected Declarations
struct msm_syncobj_post_dep
Annotated Snippet
struct msm_syncobj_post_dep {
struct drm_syncobj *syncobj;
uint64_t point;
struct dma_fence_chain *chain;
};
struct drm_syncobj **
msm_syncobj_parse_deps(struct drm_device *dev,
struct drm_sched_job *job,
struct drm_file *file,
uint64_t in_syncobjs_addr,
uint32_t nr_in_syncobjs,
size_t syncobj_stride);
void msm_syncobj_reset(struct drm_syncobj **syncobjs, uint32_t nr_syncobjs);
struct msm_syncobj_post_dep *
msm_syncobj_parse_post_deps(struct drm_device *dev,
struct drm_file *file,
uint64_t syncobjs_addr,
uint32_t nr_syncobjs,
size_t syncobj_stride);
void msm_syncobj_process_post_deps(struct msm_syncobj_post_dep *post_deps,
uint32_t count, struct dma_fence *fence);
#endif /* __MSM_GEM_SYNCOBJ_H__ */
Annotation
- Immediate include surface: `drm/drm_device.h`, `drm/drm_syncobj.h`, `drm/gpu_scheduler.h`.
- Detected declarations: `struct msm_syncobj_post_dep`.
- Atlas domain: Driver Families / drivers/gpu.
- Implementation status: source 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.