drivers/gpu/drm/nouveau/include/nvhw/class/cl507a.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/include/nvhw/class/cl507a.h

Extension

.h

Size

2017 bytes

Lines

37

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.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _cl507a_h_
#define _cl507a_h_

#define NV507A_FREE                                                             (0x00000008)
#define NV507A_FREE_COUNT                                                       5:0
#define NV507A_UPDATE                                                           (0x00000080)
#define NV507A_UPDATE_INTERLOCK_WITH_CORE                                       0:0
#define NV507A_UPDATE_INTERLOCK_WITH_CORE_DISABLE                               (0x00000000)
#define NV507A_UPDATE_INTERLOCK_WITH_CORE_ENABLE                                (0x00000001)
#define NV507A_SET_CURSOR_HOT_SPOT_POINT_OUT                                    (0x00000084)
#define NV507A_SET_CURSOR_HOT_SPOT_POINT_OUT_X                                  15:0
#define NV507A_SET_CURSOR_HOT_SPOT_POINT_OUT_Y                                  31:16
#endif // _cl507a_h

Annotation

• 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.