On 29/11/2024 13:53, Luca Ceresoli wrote:
So strictly speaking it's not an ATR, but this achieves the same.
Thanks for the extensive and very useful explanation. I had completely
missed the GMSL serder and their different I2C handling, apologies.
So, the "parent ATR" is the GMSL deser, which is not an ATR but
implementing it using i2c-atr makes the implementation cleaner. That
makes sense.
Right.
But, honestly, I can't make my mind if I like the use of ATR here or not =).
So it's not an ATR, but I'm not quite sure what it is. It's not just
that we need to change the addresses of the serializers, we need to do
that in particular way, enabling one port at a time to do the change.
If we forget about the init time hurdles, and consider the situation
after the serializers are been set up and all ports have been enabled,
we have:
There's the main i2c bus, on which we have the deserializer. The
deserializer acts as a i2c repeater (for any transaction that's not
directed to the deser), sending the messages to all serializers. The
serializers catch transactions directed at the ser, and everything else
goes through ATR and to the remote bus.
Do we have something that represents such a "i2c repeater"? I guess we
could just have an i2c bus, created by the deser, and all the sers would
be on that bus. So we'd somehow do the initial address change first,
then set up the i2c bus, and the serializer i2c clients would be added
to that bus.
Tomi
