Why a Controller Takes the Lead on a Shared Bus
When a controller and several peripherals share a communication link, they need rules about who may send data and when. The controller supplies that order: it starts an exchange, identifies the peripheral it wants, and—on many buses—provides the timing signal that keeps bits in step.
A peripheral waits until it is selected or otherwise invited to respond. That prevents two devices from driving the same signal wire at once. If both tried to set the wire to different electrical levels, the result could be corrupted data and, depending on the circuit, unnecessary electrical stress.
A Turn-Taking Rule Built Into the Wiring
In a common arrangement, the controller uses a separate select signal for each peripheral. It activates one device, sends a request, and reads the reply before selecting another. The selected device knows when its turn begins; the others keep their outputs inactive so they do not interfere.
This division of responsibility is often called a master–slave arrangement, though newer terminology may call the roles controller and peripheral. It describes communication authority, not the devices’ overall importance: a peripheral can still do substantial work on its own, but it does not initiate traffic on that shared link.
The tradeoff is straightforward. Central scheduling makes a simple shared connection predictable, but the controller must manage access—and adding peripherals can require more selection signals or more elaborate addressing. The quietest device on the bus is not necessarily idle; it is often simply waiting for the controller to give it the floor.
