-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MTL SDW AOIC fails to load topology #4906
Comments
Haha it's a bug in my own code, I added the ACPI entry in the wrong location so we select the HP Omen 14 configuration instead of the MTL SDW AOIC This was not detected because of the silly use of the tplg_name kernel parameter
@fredoh9 @marc-hb we have to stop using those kernel parameters, and track what the kernel selects. The override should ONLY be used for specific configurations. |
…figuration The new entry was added before the SDCA AOIC, which causes MTL SDW AOIC to select 2 devices only - which as a result causes a fail during the topology load. Closes: thesofproject#4906 Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
…figuration The new entry was added before the SDCA AOIC, which causes MTL SDW AOIC to select 2 devices only - which as a result causes a fail during the topology load. Closes: thesofproject#4906 Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Here's another example just for the record https://sof-ci.01.org/linuxpr/PR4902/build2084/devicetest/index.html
|
You're preaching to the choir. On the other hand, nothing there changed recently. This regression was caught in #4882 (MTLP AIOC entirely red) yet it was merged anyway. |
…figuration The new entry was added before the SDCA AOIC, which causes MTL SDW AOIC to select 2 devices only - which as a result causes a fail during the topology load. Closes: #4906 Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
this just shows that when CI provides unclear results with no logs, everyone will ignore CI results. Me included. |
Yes, the entire industry knows that by now. https://www.martinfowler.com/articles/continuousIntegration.html#FixBrokenBuildsImmediately |
From the latest kernel, we can see that 'SDW2-playback' is not created by the machine driver
This looks like either a bug in the machine driver after all the changes from @bardliao and @charleskeepax, or a problem with the topology.
I vote for the former, it's not clear to me why the microphone link is not created even though there's clearly a RT714 device listed.
The text was updated successfully, but these errors were encountered: