Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Protocol Metrics Reference
  • Protocols Glossary
  • Reading Path
  • Protocol Fundamentals25
  • AMBA Family (APB / AHB / AXI)17
  • Coherence Fabrics (ACE / CHI)17
  • Memory Interfaces (DDR / LPDDR / HBM)17
  • PCIe & CXL17
    • PCIe Layering & TLPs
    • Enumeration & Link Training
      • Enumeration & Link Training: Concepts
      • Enumeration & Link Training: Integration
      • Enumeration & Link Training: Debug
      • Enumeration & Link Training: Interview
    • CXL Attach Modes
    • PCIe / CXL Debug
    • PCIe & CXL: Tricky Q&A
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
  • Protocol Verification & Compliance21
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Enumeration & Link Training
  1. Topics
  2. Bus Protocols
  3. PCIe & CXL
  4. Enumeration & Link Training
  5. Enumeration & Link Training: Interview
On this page

    Interface ProtocolsAll levels

    Enumeration & Link Training: Interview

    Interview for Enumeration & Link Training.

    Interview drills

    Should a driver put a CPU virtual pointer directly into a DMA descriptor because its BAR registers are accessible?

    Check yourself Should a driver put a CPU virtual pointer directly into a DMA descriptor because its BAR registers are accessible?

    No. Use the platform DMA mapping API and the resulting device address; BAR accessibility does not establish DMA address translation or permissions.

    Common trap: Giving a generic fix without identifying the boundary and unmet obligation in this example.

    LTSSM reached L0 but width is wrong — what next?

    Check yourself LTSSM reached L0 but width is wrong — what next?

    Read LTSSM history and negotiated capabilities, compare configured limits, then inspect lane training and physical margins. Compare reset, clocks, firmware settings and channel conditions between boards. A lane fault is one possible cause, but reduced width alone does not prove it.

    Common trap: Blaming enumeration software first.

    Previous

    88 / 158

    Next: CXL Attach Modes

    Up next

    Up nextCXL Attach Modes

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Enumeration & Link Training: Concepts
    • Enumeration & Link Training: Integration