Can a Master issue a STOP condition regardless of whether or not a Slave has issued an acknowledgment indicating a completed transaction?

The STOP can be issued anywhere the Slave is not driving the SDA during SCL High. It may not be appropriate to do so in terms of completion of a message. But ACK and completed transaction do not belong together in I3C.

What are the I3C Bus Activity States?

The I3C Bus Activity States provide a mechanism for the Master to inform the Slaves about the expected upcoming levels of activity or inactivity on the Bus, in order to help Slaves better manage their internal states (e.g., to save power).

The four activity states and their expected activity intervals are:

  • Activity State 0: Normal activity
  • Activity State 1: Expect quiet for at least 100 µs
  • Activity State 2: Expect quiet for at least 2 ms
  • Activity State 3: Expect quiet for at least 50 ms

Can I3C Hot-Join Slave Devices be used on a legacy I²C bus?

Only if they have a way to turn off the Hot-Join feature. Hot-Join is not compatible with I2C masters, so Hot‑Join would have to be disabled for the Slave to be used on a legacy I2C bus. The disabling of the Hot‑Join feature should be done via some feature that is not part of the I3C protocol (i.e., not via the DISEC CCC), since an I2C master does not support the I3C protocol.