drivers/gpu/drm/nouveau/include/nvif/log.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/include/nvif/log.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/include/nvif/log.h- Extension
.h- Size
- 1183 bytes
- Lines
- 52
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct nvif_logstruct nvif_logsfunction nvif_log_shutdownfunction list_for_each_entry_safe
Annotated Snippet
struct nvif_log {
struct list_head entry;
void (*shutdown)(struct nvif_log *log);
};
/**
* nvif_logs - linked list of nvif_log objects
*/
struct nvif_logs {
struct list_head head;
};
#define NVIF_LOGS_DECLARE(logs) \
struct nvif_logs logs = { LIST_HEAD_INIT(logs.head) }
static inline void nvif_log_shutdown(struct nvif_logs *logs)
{
if (!list_empty(&logs->head)) {
struct nvif_log *log, *n;
list_for_each_entry_safe(log, n, &logs->head, entry) {
/* shutdown() should also delete the log entry */
log->shutdown(log);
}
}
}
extern struct nvif_logs gsp_logs;
#endif
#endif
Annotation
- Detected declarations: `struct nvif_log`, `struct nvif_logs`, `function nvif_log_shutdown`, `function list_for_each_entry_safe`.
- 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.