Thanks for your reply and sorry for the late reply, I was trying to
figure out why this log occurred, it's quite hard to reproduce.
I traced all the master and slave states, and eventually found that the behavior matches the description in commit b4cc1cbba519. The
issue has already been fixed in that commit it was caused by a state
machine bug that led to the interrupt not being handled correctly.
see: https://github.com/torvalds/linux/commit/b4cc1cbba519
(The state transitions between the master and slave here rely on
interrupts. When the signal waveform is incomplete (such as during
power off/on), it may cause state errors or brief unresponsiveness,
resulting in some log prints.)