drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_0.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_0.h

Extension

.h

Size

1620 bytes

Lines

36

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

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

Annotated Snippet

#ifndef __JPEG_V5_0_0_H__
#define __JPEG_V5_0_0_H__

#define vcnipJPEG_CGC_GATE                                 0x4160
#define vcnipJPEG_CGC_CTRL                                 0x4161
#define vcnipJPEG_SYS_INT_EN                               0x4141
#define vcnipUVD_NO_OP                                     0x0029
#define vcnipJPEG_DEC_GFX10_ADDR_CONFIG                    0x404A

extern const struct amdgpu_ip_block_version jpeg_v5_0_0_ip_block;

#endif /* __JPEG_V5_0_0_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.