drivers/gpu/drm/amd/display/dmub/inc/dmub_trace_buffer.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/display/dmub/inc/dmub_trace_buffer.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/display/dmub/inc/dmub_trace_buffer.h- Extension
.h- Size
- 2082 bytes
- Lines
- 69
- 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
dmub_cmd.h
Detected Declarations
struct dmcub_trace_buf_entrystruct dmcub_trace_bufenum dmucb_trace_code
Annotated Snippet
struct dmcub_trace_buf_entry {
enum dmucb_trace_code trace_code;
uint32_t tick_count;
uint32_t param0;
uint32_t param1;
};
#define TRACE_BUF_SIZE (1024) //1 kB
#define PERF_TRACE_MAX_ENTRY ((TRACE_BUF_SIZE - 8)/sizeof(struct dmcub_trace_buf_entry))
struct dmcub_trace_buf {
uint32_t entry_count;
uint32_t clk_freq;
struct dmcub_trace_buf_entry entries[PERF_TRACE_MAX_ENTRY];
};
#endif /* _DMUB_TRACE_BUFFER_H_ */
Annotation
- Immediate include surface: `dmub_cmd.h`.
- Detected declarations: `struct dmcub_trace_buf_entry`, `struct dmcub_trace_buf`, `enum dmucb_trace_code`.
- 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.