drivers/phy/qualcomm/phy-qcom-qmp-dp-phy-v2.h
Source file repositories/reference/linux-study-clean/drivers/phy/qualcomm/phy-qcom-qmp-dp-phy-v2.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/phy/qualcomm/phy-qcom-qmp-dp-phy-v2.h- Extension
.h- Size
- 616 bytes
- Lines
- 22
- Domain
- Driver Families
- Bucket
- drivers/phy
- 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 QCOM_PHY_QMP_DP_PHY_V2_H_
#define QCOM_PHY_QMP_DP_PHY_V2_H_
// /* Only for QMP V2 PHY - DP PHY registers */
#define QSERDES_V2_DP_PHY_AUX_INTERRUPT_MASK 0x048
#define QSERDES_V2_DP_PHY_AUX_INTERRUPT_CLEAR 0x04c
#define QSERDES_V2_DP_PHY_AUX_BIST_CFG 0x050
#define QSERDES_V2_DP_PHY_VCO_DIV 0x068
#define QSERDES_V2_DP_PHY_TX0_TX1_LANE_CTL 0x06c
#define QSERDES_V2_DP_PHY_TX2_TX3_LANE_CTL 0x088
#define QSERDES_V2_DP_PHY_SPARE0 0x0ac
#define QSERDES_V2_DP_PHY_STATUS 0x0c0
#endif
Annotation
- Atlas domain: Driver Families / drivers/phy.
- 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.