← 🔌 I/O Interface, Interrupts & DMA
Subtopic 7 of 8

9.7Handshake & bus

The idea

A bus protocol says when data is valid. Synchronous buses use a shared clock; asynchronous buses use a REQ/ACK handshake.

Think of it like this: A drill sergeant calling the beat (sync) versus passing a baton and waiting for "got it" (async).

Why it exists

The handshake lets fast and slow devices share a bus.

How it works

  1. Synchronous: every action happens on a clock edge; fast but all devices must keep up.
  2. Asynchronous: master raises REQ, slave raises ACK, master drops REQ, slave drops ACK.
  3. Each step waits for the previous one: self-timed.

Worked example: Handshake

Four-phase: REQ↑, ACK↑, REQ↓, ACK↓.

Now play with it

  • →Switch between the two tabs and step through.
Master-
REQ line0
ACK line0
Slave-
  • Master puts address/data on the bus
  • Master raises REQ: "my data is valid"
  • Slave sees REQ, takes the data (at its own speed)
  • Slave raises ACK: "I have it"
  • Master drops REQ
  • Slave drops ACK: transfer complete, ready for the next

Self-timed: fast and slow devices can share the bus. Costs extra handshake time.

Check yourself

An asynchronous bus synchronises transfers using:

Remember: Sync = clock; async = handshake.
Exam notes (the dense version)

Synchronous bus (clocked, fast, needs equal speeds) vs asynchronous (REQ/ACK handshake, flexible).

Previous year questions: I/O Interface, Interrupts & DMA (8)

PYQs are grouped by topic, so this is the full set for I/O Interface, Interrupts & DMA; try the ones that match this subtopic. Open all 8 on the topic page.