-
Notifications
You must be signed in to change notification settings - Fork 349
topology: cleanup/align SoundWire device numbers #3806
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
topology: cleanup/align SoundWire device numbers #3806
Conversation
naveen-manohar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With UCM changes, Verified Basic Audio on Volteer-SDW - sof-tgl-sdw-max98373-rt5682.tplg
|
@bardliao @RanderWang can you take a look on other SoundWire devices? |
|
I tested 3 sdw laptops and all of them looks good to me. |
@bardliao why only 3 HDMI for tgl device ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PCM8 for iDisp4 is missed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PCM8 ?
|
it is ok on Volteer |
|
@naveen-manohar are you saying we alos need an UCM update here ? |
Yes Volteer will need a UCM update, but that was shared and accepted by the Chrome folks. The Volteer configuration is not in alsa-ucm-conf upstream so platforms which are handled upstream, such as Dell/HP, have priority. |
yes, I managed to self-conflict between PRs. I need to change device names as well. |
Post this PR merge, shall take to Chrome Tree & submit along with UCM change. |
|
@plbossart fyi - some merge conflicts. |
yes, will work on this later today. |
This topology is no longer used and productized, let's remove it. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
This file was used for early enablement of SoundWire on a platform, before we had support for amplifiers. This is no longer needed, let's remove it. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Confusion between input and output, and PCM name and pipeline ID. Copy/paste likely here. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Add macro to allow the use of "BufferedMic" instead of "DMIC16kHz" in KPB usages. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
This patch follows the suggested layout: PCM0 playback Jack PCM1 capture Jack PCM2 playback Speaker PCM3 capture Amplifier Reference (typically based on I/V feedback) PCM4 capture Microphone PCM5 playback HDMI 1 PCM6 playback HDMI 2 PCM7 playback HDMI 3 PCM8 playback HDMI 4 PCM9 RESERVED PCM10 capture DMIC PCM11 capture DMIC16kHz PCM12 capture BufferedMic (aka KPB) PCM13 playback Bluetooth PCM14 capture Bluetooth PCM40 playback Speaker 2 (non-aggregated) Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Align on the following names: PCM0 playback Jack PCM1 capture Jack PCM2 playback Speaker PCM3 capture Amplifier Reference (typically based on I/V feedback) PCM4 capture Microphone PCM5 playback HDMI 1 PCM6 playback HDMI 2 PCM7 playback HDMI 3 PCM8 playback HDMI 4 PCM9 RESERVED PCM10 capture DMIC PCM11 capture DMIC16kHz PCM12 capture BufferedMic (aka KPB) PCM13 playback Bluetooth PCM14 capture Bluetooth Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
a9acd04 to
43e182d
Compare
|
@lgirdwood we should have been more careful on this one, CI tests did show a problem with alsa-bat precisely due to the device number issues. https://sof-ci.01.org/sofpr/PR3806/build8108/devicetest/ I only realized this with the daily test and @fredoh9 's help. good old alsa-bat still has its value. All other tests don't seem to check for expected device numbers or names. |
|
@plbossart thanks, fwiw, I've been seeing this all week and I've created an issue for CI test to dump PCM and card names when this happens. Do you have a followup for UCM ? or do you want to revert and hold for v1.8 ? |
I have a followup coming, @ranj063 helped me find the issues in current topologies that were exposed by my changes. |

No description provided.