drivers/gpu/drm/msm/registers/display/msm.xml
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/msm/registers/display/msm.xml
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/msm/registers/display/msm.xml- Extension
.xml- Size
- 802 bytes
- Lines
- 33
- 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="http://nouveau.freedesktop.org/ rules-ng.xsd">
<import file="freedreno_copyright.xml"/>
<doc>
Register definitions for the display related hw blocks on
msm/snapdragon
</doc>
<!--
<enum name="chipset">
<value name="MDP40"/>
<value name="MDP50"/>
</enum>
-->
<import file="mdp4.xml"/>
<import file="mdp5.xml"/>
<import file="dsi.xml"/>
<import file="dsi_phy_28nm_8960.xml"/>
<import file="dsi_phy_28nm.xml"/>
<import file="dsi_phy_20nm.xml"/>
<import file="dsi_phy_14nm.xml"/>
<import file="dsi_phy_10nm.xml"/>
<import file="dsi_phy_7nm.xml"/>
<import file="sfpb.xml"/>
<import file="hdmi.xml"/>
<import file="edp.xml"/>
</database>
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.