PSA: we've got a couple projects switching from I²C "master/slave" to "initiator/target" already, so if you're looking for more accurate and descriptive nomenclature, consider these :) https://github.com/fwupd/fwupd/pull/2244 … https://github.com/GlasgowEmbedded/glasgow/commit/5a53dc1649a238cbf6d2f21ba599635579387f89 …
Keep in mind that although a priori it might feel like the initiator controls the bus, it doesn't. The target can use clock stretching to change the clock rate too, or refuse to ACK anything. And data transfers are symmetric after the initial address cycle.
-
-
So the initiator's job is really just to start and end transactions, and *suggest* a clock rate. That's why it's a fitting term, because it really just starts the conversation but doesn't have that much control.
-
And of course with multi-master devices can switch roles. I've even seen a device use an I²C bus as a broadcast packet network.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.