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
dai_ssp_set_reg_config: SSPx configuration: Ignoring SSCR1:TSRE SSCR1:RSRE from blob #9026
Seems to be printed multiple times in most (passing!) tests on LNL, for instance daily run #/result/planresultdetail/39547?model=LNLM_RVP_NOCODEC&testcase=check-playback-100sec
It's not LNL-specfic. I just re-ran thesofproject/sof-test#1075 and I spotted it on MTLP_RVP_NOCODEC. I'll post the link to the full report there once the test run is complete.
Activity
marc-hb commentedon Apr 9, 2024
This is probably old. We never noticed because we've never caught firmware errors yet:
plbossart commentedon Apr 9, 2024
are you sure it's LNL-specific? I think it's a feature of the SSP firmware driver, the blob ignores the bits that enable transmission.
One could also argue it's possibly the blob that sets those bits in the config - and that's probably a mistake?
marc-hb commentedon Apr 9, 2024
It's not LNL-specfic. I just re-ran thesofproject/sof-test#1075 and I spotted it on
MTLP_RVP_NOCODEC. I'll post the link to the full report there once the test run is complete.[-][LNL] dai_ssp_set_reg_config: SSPx configuration: Ignoring SSCR1:TSRE SSCR1:RSRE from blob[/-][+][LNL,MTL] dai_ssp_set_reg_config: SSPx configuration: Ignoring SSCR1:TSRE SSCR1:RSRE from blob[/+]marc-hb commentedon Apr 9, 2024
Armed with that new knowledge, I just found a complete, public, MTL test run that has the same error:
https://sof-ci.01.org/sofpr/PR8956/build3506/devicetest/index.html?model=MTLP_RVP_NOCODEC&testcase=check-playback-10sec
marc-hb commentedon Apr 10, 2024
Just seen on TGL too:
https://sof-ci.01.org/softestpr/PR1172/build276/devicetest/index.html?model=TGLU_RVP_NOCODEC-ipc4&testcase=check-playback-10sec
marc-hb commentedon Apr 10, 2024
Based on thesofproject/sof-test#1075 (comment) results this seems to be a NOCODEC thing.
NOCODEC reproduction rate: 100%
"codec" reproduction rate: 0%
[-][LNL,MTL] dai_ssp_set_reg_config: SSPx configuration: Ignoring SSCR1:TSRE SSCR1:RSRE from blob[/-][+]dai_ssp_set_reg_config: SSPx configuration: Ignoring SSCR1:TSRE SSCR1:RSRE from blob[/+]3 remaining items
marc-hb commentedon Apr 10, 2024
So, just downgrade to the message to WARN level?
plbossart commentedon Apr 10, 2024
Warn is even too high IMHO, it's a known behavior. Nothing different to expect. dev_dbg() is probably fine.
marc-hb commentedon Apr 11, 2024
The LOG_ERR was actually added by zephyrproject-rtos/zephyr@6423bc3bc885 and the level looks clearly unintentional there. I'm submitting a fix.
drivers: dai: intel: ssp: fix LOG_ERR level / false positive
ujfalusi commentedon Apr 11, 2024
The
dai_intel_ssp: dai_ssp_set_reg_config: SSP2 configuration:is in wrong level, it should be info, sending a fix right away.ujfalusi commentedon Apr 11, 2024
@marc-hb, I see you already done that, thanks!
drivers: dai: intel: ssp: fix LOG_ERR level / false positive
drivers: dai: intel: ssp: fix LOG_ERR level / false positive
lgirdwood commentedon Apr 16, 2024
@marc-hb can we close ?
marc-hb commentedon Apr 16, 2024
I don't think we've updated Zephyr that far yet.
EDIT: indeed not yet, manifest still at Zephyr commit 2ccf775396c2 right now.
marc-hb commentedon Apr 23, 2024
Zephyr updated, we have the fix now. INF level in https://sof-ci.01.org/softestpr/PR1075/build327/devicetest/index.html
drivers: dai: intel: ssp: fix LOG_ERR level / false positive