drivers/gpu/drm/nouveau/dispnv50/crcc37d.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/dispnv50/crcc37d.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/dispnv50/crcc37d.h- Extension
.h- Size
- 854 bytes
- Lines
- 41
- 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
linux/types.hcrc.h
Detected Declarations
struct crcc37d_notifierstruct crcc37d_entry
Annotated Snippet
struct crcc37d_notifier {
u32 status;
/* reserved */
u32:32;
u32:32;
u32:32;
u32:32;
u32:32;
u32:32;
u32:32;
struct crcc37d_entry {
u32 status[2];
u32:32; /* reserved */
u32 compositor_crc;
u32 rg_crc;
u32 output_crc[2];
u32:32; /* reserved */
} entries[CRCC37D_MAX_ENTRIES];
} __packed;
int crcc37d_set_ctx(struct nv50_head *head, struct nv50_crc_notifier_ctx *ctx);
u32 crcc37d_get_entry(struct nv50_head *head, struct nv50_crc_notifier_ctx *ctx,
enum nv50_crc_source source, int idx);
bool crcc37d_ctx_finished(struct nv50_head *head, struct nv50_crc_notifier_ctx *ctx);
#endif /* !__CRCC37D_H__ */
Annotation
- Immediate include surface: `linux/types.h`, `crc.h`.
- Detected declarations: `struct crcc37d_notifier`, `struct crcc37d_entry`.
- 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.