You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[SDW] IO timeout when stopping clock after S2idle suspend/resume #1609
The dmesg log shows an IO timeout when stopping the clock the second time, but when looking at the logs the clock stop command is retried and will succeed when re-issued by do_transfer()
This makes me think the state is not properly restored when doing a system resume after a clock stop done in pm_runtime suspend
@plbossart yes, it is caused by FIFO_LEVEL register setting. the detail:
CDNS_MCP_FIFOLEVEL was set to 2, and after S2idle, we send cmd with count =1 & msg_count = 1, so we don't set this register correctly. I will check it later.
Activity
RanderWang commentedon Dec 10, 2019
@plbossart yes, it is caused by FIFO_LEVEL register setting. the detail:
CDNS_MCP_FIFOLEVEL was set to 2, and after S2idle, we send cmd with count =1 & msg_count = 1, so we don't set this register correctly. I will check it later.
RanderWang commentedon Dec 11, 2019
@plbossart fixed by plbossart#10
RanderWang commentedon Dec 11, 2019
a PR for branch soundwire-bug-fixes is #1618
YvonneYang2 commentedon Dec 11, 2019
Tested it with integretion/soundwire-latest(e375909) + #1586 + #1618 , issue cannot be reproduced.
RanderWang commentedon Dec 12, 2019
Fixed by PR #1618