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
Describe the bug
Buffer's are shown to be on Core: 0 in the topology viewer. They are passive components and do not have a core associated with them. It is confusing for people to see buffers and components in the same pipeline to have different core ID's
I think it's because those buffer components (like BUF7.0, BUF11.0, etc.) actually contain the element with token SOF_TKN_COMP_CORE_ID. If the component doesn't contain the core ID data, the graph won't show it, like BUF1.0, BUF2.1, etc. Therefore, I think the better way is to remove the core ID data from buffer components.
It seems there are some historic reasons to allocate buffers on core 0 thesofproject/sof#5097. If it's unacceptable to remove buffer core ID from the source code, I can add an exception for the buffer components in the topology graph.
Describe the bug
Buffer's are shown to be on Core: 0 in the topology viewer. They are passive components and do not have a core associated with them. It is confusing for people to see buffers and components in the same pipeline to have different core ID's
To Reproduce
Just view the topology graph for the sof-cavs-nocodec.tplg
https://sof-ci.01.org/sofpr/PR5958/build751/devicetest/?model=ADLP_RVP_NOCODEC&testcase=check-playback-10sec
Expected behavior
Buffers show no core ID
The text was updated successfully, but these errors were encountered: