drivers/phy/qualcomm/phy-qcom-qmp-pcs-pcie-v6_30.h
Source file repositories/reference/linux-study-clean/drivers/phy/qualcomm/phy-qcom-qmp-pcs-pcie-v6_30.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/phy/qualcomm/phy-qcom-qmp-pcs-pcie-v6_30.h- Extension
.h- Size
- 1002 bytes
- Lines
- 26
- 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_PCS_PCIE_V6_30_H_
#define QCOM_PHY_QMP_PCS_PCIE_V6_30_H_
/* Only for QMP V6_30 PHY - PCIE have different offsets than V6 */
#define QPHY_PCIE_V6_30_PCS_POWER_STATE_CONFIG2 0x014
#define QPHY_PCIE_V6_30_PCS_TX_RX_CONFIG 0x020
#define QPHY_PCIE_V6_30_PCS_ENDPOINT_REFCLK_DRIVE 0x024
#define QPHY_PCIE_V6_30_PCS_OSC_DTCT_ACTIONS 0x098
#define QPHY_PCIE_V6_30_PCS_EQ_CONFIG1 0x0a8
#define QPHY_PCIE_V6_30_PCS_G3_RXEQEVAL_TIME 0x0f8
#define QPHY_PCIE_V6_30_PCS_G4_RXEQEVAL_TIME 0x0fc
#define QPHY_PCIE_V6_30_PCS_G4_EQ_CONFIG5 0x110
#define QPHY_PCIE_V6_30_PCS_G4_PRE_GAIN 0x164
#define QPHY_PCIE_V6_30_PCS_RX_MARGINING_CONFIG1 0x184
#define QPHY_PCIE_V6_30_PCS_RX_MARGINING_CONFIG3 0x18c
#define QPHY_PCIE_V6_30_PCS_RX_MARGINING_CONFIG5 0x194
#define QPHY_PCIE_V6_30_PCS_G3_FOM_EQ_CONFIG5 0x1b4
#define QPHY_PCIE_V6_30_PCS_G4_FOM_EQ_CONFIG5 0x1c8
#endifAnnotation
- 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.