WHY a figure before the questions: almost every trap below is really a confusion about where on the curve we are measuring. Look at the two edges once, and the answers stop being memorized rules.
The blue curve is the exponential fall V(t)=VDDe−t/τ with τ=ReqCL. The green dashed line marks the 50% level (where tpHL is read — the logic decision point). The orange band marks 90% down to 10% (where tf is read — the edge shape). Notice the curve flattens toward the bottom rail: it approaches0 but never touches it — that is why 0%–100% time is infinite and we clip to 10–90%.
This second figure derives the famous ratio: reading tpHL off the 50% crossing gives τln2; reading tf across the 90%→10% span gives τln9. The τ=ReqCL cancels in the ratio, leaving tf/tpHL=ln9/ln2≈3.17 for every pure exponential, regardless of device.
The third figure is the slew trap: a slow input (red) keeps both NMOS and PMOS partly on at once (the shaded overlap where both gate-drives sit near threshold). During that overlap the pull-down current is stolen by the fighting pull-up, so the output reaches its 50% point later — real delay grows with input slope.
Answer each with T/F and one sentence of why — never a bare verdict.
True or false: A logic gate switches its output instantly the moment the input crosses threshold.
False. The output node has capacitance CL and the transistor supplies only finite current, so CLdV/dt=i forces a nonzero charging time — the delay.
True or false: Doubling only the load capacitance CL (transistor unchanged) doubles the propagation delay.
True. Both models give tp∝CL (0.69ReqCL or CLVDD/2IDSAT), and neither the equivalent resistance Req nor the saturation current IDSAT depends on the load, so delay scales linearly with CL.
True or false: For a pure RC (exponential) output, the fall time tf is always exactly 3.17× the delay tpHL.
True.tf/tpHL=ln9/ln2≈3.17 (see figure s02), a ratio fixed by the 10–90% vs 50% definitions — it cancels ReqCL entirely and is independent of the device.
True or false: Making both NMOS and PMOS wider always makes a chip faster.
False. Wider transistors lower yourReq but raise your gate's own input capacitance, which becomes the load the previous stage must drive — you can slow the stage before you.
True or false: In a symmetric (matched) inverter with tr=tf, the NMOS and PMOS have equal widths.
False. Because μn≈2μp, matching requires Wp≈2Wn so that Reqp=Reqn; equal widths would leave the PMOS about twice as resistive.
True or false: Propagation delay depends on the input's own rise/fall speed.
True (in reality). The idealized formulas assume a step input, but a slow input keeps both transistors partly on longer (figure s03), so real delay grows with input slope — this is why slew propagates down a chain.
True or false: Rise time and propagation delay measure the same physical thing from different start points.
False. Delay is a causal lag between two nodes (input-50% → output-50%); rise/fall is the steepness of one edge (10%→90% of the output alone) — they answer different questions.
True or false: A larger equivalent resistance Req improves (reduces) delay.
False.tp∝Req, so larger Req (a weaker, narrower transistor) means slower switching; Req∝1/W, so you want it small.
"Rise time is the time for the output to swing from 0% to 100% of VDD."
The output approaches the rail asymptotically (exponentially, see figure s01), so it never truly reaches 0% or 100% — that time is infinite; the convention clips to 10%–90%.
"Since delay is 0.69ReqCL, I'll use the transistor's small-signal on-resistance at VDS=0 for Req."
The equivalent resistance Req is an average of V/I over the whole swing (near-saturation at the start, triode at the end), not the tiny-VDS triode resistance — that would badly underestimate delay.
"Delay is measured at 50% because the output is exactly halfway, which is easiest to see on a scope."
The real reason is logical, not visual: VDD/2 is the switching threshold of the next gate — the voltage at which it flips its decision.
"tpHL=CLVDD/(2IDSAT) uses VDD/2 because half the transistors are conducting."
The VDD/2 appears because delay is measured only to the halfway point, so only half the voltage swing's worth of charge must be moved — it has nothing to do with device count.
"Adding a buffer stage always increases total path delay because it adds a gate."
For a very large load, one small gate is crippled by CL/drive; a chain of progressively sized buffers can drive the load faster overall — delay tracks CL/drive, not gate count.
"To cut delay in half, just shrink the transistor width to lower its gate capacitance."
Shrinking WraisesReq∝1/W, which slows the pull-down of its own output — the reduced input cap only helps the previous stage.
"Since NMOS and PMOS in an inverter both drive the same CL, tpHL=tpLH automatically."
Only if the resistances match; with equal widths the PMOS is ~2× more resistive, so tpLH>tpHL unless you size Wp=2Wn.
Why does the factor ln2 (≈0.69) appear in the RC delay but ln9 (≈2.2) in the fall time?
Delay crosses one point (50%), giving −ln(1/2)=ln2; fall time spans two points (90% down to 10%), giving ln(0.9/0.1)=ln9 — the log of the ratio of the two clip levels (figure s02).
Why do the RC model and the constant-current model give the same proportionalitytp∝CL/drive despite different physics?
Both come from CLdV/dt=−i; whether i falls exponentially (resistor Req) or stays constant (saturation current IDSAT), the time to move a fixed charge CLΔV still scales as charge over current.
Why does the PMOS being weaker mean the pull-up (rising) edge is naturally slower than the pull-down?
Weaker PMOS ⇒ larger Reqp ⇒ larger tpLH=0.69ReqpCL, so the low→high transition lags the high→low unless the PMOS is widened.
Why is the overall gate delay defined as the averagetp=21(tpHL+tpLH) rather than one of them?
A gate's output rises on some switches and falls on others; the average represents the typical delay a signal experiences regardless of edge direction.
Why does a slow (slowly-changing) input signal increase a gate's delay?
While the input lingers near threshold, both transistors conduct simultaneously (the shaded overlap in figure s03), the pull-up fights the pull-down and wastes current, delaying the moment the output reaches its own 50% point.
Why do we care about the slowest path's delay for maximum clock frequency, not the average?
The clock period must be long enough for every signal to settle before the next edge; the slowest (critical) path sets that limit, so it alone caps the frequency.
Why does doubling Wnot necessarily double the speed of a real gate driving the next identical gate?
Doubling W halves Req but also doubles the gate's own input capacitance, so the load presented to the previous stage doubles too — the net speedup is diluted (this is the fan-out-of-4 tradeoff).
What happens to tf (10%→90% time) if CL→0 (no load)?
It →0: with nothing to charge, the exponential's time constant ReqCL→0, so the edge becomes ideally sharp (real parasitics keep it finite).
What is the theoretical 0%→100% transition time for a pure RC output?
Infinite — the exponential VDDe−t/τ approaches the rail but never equals it (figure s01), which is exactly why the 10–90% clip is used.
If Reqn=Reqp (perfectly matched inverter), what is the relation between tpHL and tpLH?
They are equal, so the average gate delay tp equals each individually and the output edges are symmetric.
For a degenerate "infinitely strong" transistor (Req→0 or IDSAT→∞), what is the delay?
Zero — but this is unphysical; real transistors have finite W/L and current, so delay is always positive.
If the input is a perfect step but the output still takes time, where does that time come from?
Entirely from the RC charging of CL through the transistor — the delay is an intrinsic property of the output node, not of the input's speed.
Which second-order effects can shift the realReq away from the ideal 43VDD/IDSAT estimate?
Channel-length modulation (λ) makes IDSAT creep up with VDS, lowering Req; body effect raises the threshold VT of a stacked transistor (its source is above ground), weakening it and raising Req; and VT shifts from temperature or process lower the drive and raise Req at hot/slow corners.
Why does a transistor stacked above another (its source not at ground) drive more weakly, raising the path's Req?
Body effect: with the source lifted above the body voltage, the effective threshold VT rises, so VGS−VT (the overdrive) shrinks and the delivered current IDSAT drops — the equivalent resistance climbs.
Recall The three "same word, different meaning" traps
50% vs 10–90%: delay uses 50% (logic threshold across two nodes); rise/fall use 10–90% (edge shape on one node).
ln2 vs ln9: one crossing vs a span of two clip levels.
Wider W: helps your output (Req↓) but hurts the stage feeding you (input cap ↑).
Recall What
Req and IDSAT actually mean
Req ::: the average V/I of the on-transistor over the swing, letting us treat it as a plain resistor; Req∝1/(W/L).
IDSAT ::: the near-constant saturation current (tens–hundreds of μA) the device delivers when VDS is large — the "drive strength".