summaryrefslogtreecommitdiff
path: root/scripts/stackusage
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2025-12-16 20:57:21 +0000
committerMark Brown <broonie@kernel.org>2025-12-16 20:57:21 +0000
commite3b88652b66b6b899eb1049694b214267b4e6c79 (patch)
treeb643e83181e081f3aa70b0babbf9eee66e14ce89 /scripts/stackusage
parent544c0494cdb3732281e1f2e279cfa561724355db (diff)
parent91b7f7d0eedaaa8993e662c4c6db9b3cfe8a2faf (diff)
ASoC: Intel: common / SOF: Use function topologies for
Merge series from Peter Ujfalusi <peter.ujfalusi@linux.intel.com>: support for NVL-S and the support using functional topology fragments for Soundwire configurations is introduced in 6.19-rc1 in parallel. The SOF projects plan is to not create individual topology files for NVL as with SDCA and the functional topology support can handle most if not all soundwire devices going forward. However one issue have been identified with the functional topology only support, which was masked by the presence of a single topology file: if the device contains a dai link for which we don't have topology fragment, then the probe will fail. This worked with a fallback to a monolithic topology file - which made the dai link to be ignored. The first patch in the series adds a flag to instruct the function discovery to make a best effort to form a card by ignoring functions without corresponding fragment (and print this out for developers) in case there is no fallback topology available. The second patch removes the match entry to refer to a topology file which will not be built by the SOF project.
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions