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
kv2019i opened this issue
Mar 14, 2023
· 5 comments
Assignees
Labels
bugSomething isn't working as expectedCPC CPSIPC4Issues observed with IPC4 (same IPC as Windows)MTLApplies to Meteor Lake platformP2Critical bugs or normal features
Describe the bug
The CPS/CPS values for MTL are incorrect for multiple modules. Currently the DSP FW does not adjust DSP speed based on this data, but when this feature is enabled, the incorrect data will lead to running DSP at too low/high frequency, leading to either audio artifacts, or too high power consumption.
To Reproduce
Need in-progress code for FW -> #7267
Reproduction Rate
100%
Expected behavior
Values should be closer to those used on mtl-004 branch of rimage
96ed61016a6fb3551b6013ccbb0a4935ae494f07 (origin/mtl-004-drop-stable) mtl: fill in cps and cpc data for smart_amp_test module
f59cf6fa05156ed9e5f404f2e599746d5e8573b5 mtl: fill in cps and cpc data for ASRC module
0bcef6fea4d9592d7d9ee4b5847c1960a97d6052 mtl: fill in subsequent measured cps and mcps data
The text was updated successfully, but these errors were encountered:
kv2019i
added
bug
Something isn't working as expected
P2
Critical bugs or normal features
IPC4
Issues observed with IPC4 (same IPC as Windows)
MTL
Applies to Meteor Lake platform
labels
Mar 14, 2023
Note, updated titles, "struct ipc4_base_module_cfg" has only the CPC value, so CPS is not relevant here (unless it's used as a source to calculate CPC).
kv2019i
changed the title
[BUG][IPC4] Incorrect CPC/CPS values for MTL
[BUG][IPC4] Incorrect CPC values for MTL
Mar 14, 2023
This is the PR under review, according to Liam's suggestion:
"Liam suggest to use max peak + 10% margin as clock scaling cannot bring much power saving unless using 38.4MHz WoV clock"
After this was merged, we can update part of module CPC based on CI performance data.
Closing this bug. the CPC (cycle budget per audio module) values are now close enough and there are no kernel warnings from missing values with mainline firmware and topology anymore. Continue maintenance of accurate CPC data with #8019 which is enabling DSP speed control driver by the cycle-budgets.
bugSomething isn't working as expectedCPC CPSIPC4Issues observed with IPC4 (same IPC as Windows)MTLApplies to Meteor Lake platformP2Critical bugs or normal features
Describe the bug
The CPS/CPS values for MTL are incorrect for multiple modules. Currently the DSP FW does not adjust DSP speed based on this data, but when this feature is enabled, the incorrect data will lead to running DSP at too low/high frequency, leading to either audio artifacts, or too high power consumption.
To Reproduce
Need in-progress code for FW -> #7267
Reproduction Rate
100%
Expected behavior
Values should be closer to those used on mtl-004 branch of rimage
https://github.com/thesofproject/rimage/tree/mtl-004-drop-stable
FYI @abonislawski @mwasko @ujfalusi @lgirdwood @kfrydryx @pblaszko
The text was updated successfully, but these errors were encountered: