BeginnerQuestion 82 of 187

What is a clock mesh driver, and how is it different from a tap driver?

From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide

By Tabish Iqbal, who has 9+ years of VLSI Physical Design experience

Short Answer

A mesh driver feeds the clock mesh itself -- the 2D grid of horizontal and vertical straps joined by vias at intersections -- and is inserted via create_clock_drivers with -short_outputs to tie all driver outputs together for the mesh. A tap driver is different: it's what feeds a local subtree off the mesh in a regular multisource clock tree, connected to the mesh but driving downstream logic, not the mesh grid itself.

Technical Reference DiagramWhat is a clock mesh driver, and how is it different from a tap driver?

Technical Explanation

  • A mesh driver feeds the clock mesh itself -- the 2D grid of horizontal and vertical straps joined by vias at intersections.
  • Mesh drivers are inserted via create_clock_drivers with -short_outputs, which ties all driver outputs together specifically for feeding a mesh.
  • A tap driver is different: it feeds a local subtree off the mesh in a regular multisource clock tree -- connected to the mesh, but driving downstream logic rather than the mesh grid itself.
  • Both use the same create_clock_drivers command, just with different options (-short_outputs for mesh, -boxes/-lib_cells for taps) -- the command doesn't have separate names for the two roles.

Common Mistake

The Trap: Assuming "clock driver" always means the same thing -- mesh drivers and tap drivers use the same command but serve genuinely different structural roles.

Follow-up Question & Model Response

"If both use create_clock_drivers, what option specifically distinguishes inserting a mesh driver from inserting a tap driver?"

Candidate Model Response: -short_outputs is the option specific to mesh drivers -- it ties all driver outputs together for the mesh; tap drivers use -boxes/-lib_cells for grid placement without that output-tying behavior.

Practical Example

Debug Scenario: A multisource clock tree's mesh looks correctly built, but downstream subtrees show unexpected latency -- checking the tap drivers (not the mesh drivers, which were already confirmed correct) is where the actual problem turns out to be.

PnR Flow Mentor Guide

Read the complete 8-chapter PnR Flow Mentor Guide free on the web — library setup through placement, clock tree synthesis, routing, chip finishing, hierarchical implementation, and ECO, all the way to stream-out.

Explore PnR Flow Mentor Guide →

Offline PDF Bundle

Want all 1109 questions offline?

Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.

See what's inside the bundle
PnR Flow Physical Design Mentor Guide — eight chaptersPnR Flow Mentor GuideEight chapters, library setup through to stream-out.

Continue practising

Related PnR (Place & Route) questions

BeginnerWhat makes a generated clock different from a primary clock?BeginnerHow are clock tree DRC constraints different from clock tree timing constraints, and why does CTS need both?IntermediateIf you need to rebuild a clock tree from scratch, what does remove_clock_trees actually preserve versus remove?ExpertWhat is CCD (Concurrent Clock and Data optimization), and what does it actually change in the clock tree?