Hello,
And good point. On I2C, it was possible to use an information of direction through a specific callback named
HAL_I2C_AddrCallback.
At I2C driver level, it works as the Stretch mode is used and so it was possible to "delay" the Master/slave communication until Slave was ready to receive or transmit data.
On I3C level, link to MIPI specification the stretch mode is forbidden. So it is not possible to delay a started private communication. So not possible to have a delay to inform application that a private transmit or receive communication is requested.
The best way to perform an unknown communication direction, is:
To manage a protocol on application side like:
Controller send a first specific transmit with a Code which can be detected like a transmit or receive at next communication.
And then at Target side, thx to this received code, the target will be able to prepare the private communication to a transmit or a receive.
This start of communication by using function
HAL_I3C_Tgt_Transmit_IT or HAL_I3C_Tgt_Receive_IT can be called inside the HAL_I3C_TgtRxCpltCallback.
Hope it helps, MIPI I3C add some private communication restriction in comparison of I2C as no stretch is possible.
Regards
