i2cConfig clarification

[nebrius]

In the documentation for i2cConfig, I noticed that it's possible to specify the bus, port, and address. Perhaps I'm missing something that's in the I2C spec, but what is port and how is it different from bus?

[fivdi]

To the best of my knowledge port was added for tessel-io. A Tessel has two I2C buses, one on port A and one on port B. The corresponding bus numbers are 4 and 2 respectively. The user facing names for the buses are the port names A and B rather than the bus numbers 4 and 2. See i2cConfig in tessel-io for further details.

[nebrius]

Ahhh, that makes sense. In that case, we should clarify in the documentation. Let's leave this issue open as a reminder

[rwaldron]

Can we say: bus is port is bus? Allow either to mean the same? Is that sloppy, lazy?

[fivdi]

Can we say: bus is port is bus? Allow either to mean the same? Is that sloppy, lazy?

Saying bus is port is bus works on a Tessel 2 because each port has one I2C bus. If there are other boards using the term port and they have ports with no I2C bus or more than one I2C bus then things will get awkward (or sloppy.)

[nebrius]

If there are other boards using the term port and they have ports with no I2C bus or more than one I2C bus

Correct me if I'm wrong, but it sounds like port is a friendly alias for bus, meaning that by definition they should always be 1:1, correct?