drivers/gpu/drm/msm/registers/adreno/a4xx.xml
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/msm/registers/adreno/a4xx.xml
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/msm/registers/adreno/a4xx.xml- Extension
.xml- Size
- 113484 bytes
- Lines
- 2410
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: drivers/gpu
- Status
- atlas-only
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
<?xml version="1.0" encoding="UTF-8"?>
<database xmlns="http://nouveau.freedesktop.org/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://gitlab.freedesktop.org/freedreno/ rules-fd.xsd">
<import file="freedreno_copyright.xml"/>
<import file="adreno/adreno_common.xml"/>
<import file="adreno/adreno_pm4.xml"/>
<enum name="a4xx_color_fmt">
<value name="RB4_A8_UNORM" value="0x01"/>
<value name="RB4_R8_UNORM" value="0x02"/>
<value name="RB4_R8_SNORM" value="0x03"/>
<value name="RB4_R8_UINT" value="0x04"/>
<value name="RB4_R8_SINT" value="0x05"/>
<value name="RB4_R4G4B4A4_UNORM" value="0x08"/>
<value name="RB4_R5G5B5A1_UNORM" value="0x0a"/>
<value name="RB4_R5G6B5_UNORM" value="0x0e"/>
<value name="RB4_R8G8_UNORM" value="0x0f"/>
<value name="RB4_R8G8_SNORM" value="0x10"/>
<value name="RB4_R8G8_UINT" value="0x11"/>
<value name="RB4_R8G8_SINT" value="0x12"/>
<value name="RB4_R16_UNORM" value="0x13"/>
<value name="RB4_R16_SNORM" value="0x14"/>
<value name="RB4_R16_FLOAT" value="0x15"/>
<value name="RB4_R16_UINT" value="0x16"/>
<value name="RB4_R16_SINT" value="0x17"/>
<value name="RB4_R8G8B8_UNORM" value="0x19"/>
<value name="RB4_R8G8B8A8_UNORM" value="0x1a"/>
<value name="RB4_R8G8B8A8_SNORM" value="0x1c"/>
<value name="RB4_R8G8B8A8_UINT" value="0x1d"/>
<value name="RB4_R8G8B8A8_SINT" value="0x1e"/>
<value name="RB4_R10G10B10A2_UNORM" value="0x1f"/>
<value name="RB4_R10G10B10A2_UINT" value="0x22"/>
<value name="RB4_R11G11B10_FLOAT" value="0x27"/>
<value name="RB4_R16G16_UNORM" value="0x28"/>
<value name="RB4_R16G16_SNORM" value="0x29"/>
<value name="RB4_R16G16_FLOAT" value="0x2a"/>
<value name="RB4_R16G16_UINT" value="0x2b"/>
<value name="RB4_R16G16_SINT" value="0x2c"/>
<value name="RB4_R32_FLOAT" value="0x2d"/>
<value name="RB4_R32_UINT" value="0x2e"/>
<value name="RB4_R32_SINT" value="0x2f"/>
<value name="RB4_R16G16B16A16_UNORM" value="0x34"/>
<value name="RB4_R16G16B16A16_SNORM" value="0x35"/>
<value name="RB4_R16G16B16A16_FLOAT" value="0x36"/>
<value name="RB4_R16G16B16A16_UINT" value="0x37"/>
<value name="RB4_R16G16B16A16_SINT" value="0x38"/>
<value name="RB4_R32G32_FLOAT" value="0x39"/>
<value name="RB4_R32G32_UINT" value="0x3a"/>
<value name="RB4_R32G32_SINT" value="0x3b"/>
<value name="RB4_R32G32B32A32_FLOAT" value="0x3c"/>
<value name="RB4_R32G32B32A32_UINT" value="0x3d"/>
<value name="RB4_R32G32B32A32_SINT" value="0x3e"/>
<value name="RB4_NONE" value="0xff"/>
</enum>
<enum name="a4xx_tile_mode">
<value name="TILE4_LINEAR" value="0"/>
<value name="TILE4_2" value="2"/>
<value name="TILE4_3" value="3"/>
</enum>
<enum name="a4xx_vtx_fmt" prefix="chipset">
<!-- hmm, shifted one compared to a3xx?!? -->
Annotation
- Atlas domain: Driver Families / drivers/gpu.
- Implementation status: atlas-only.
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.