Skip to content

Conversation

@plbossart
Copy link
Member

Add a kernel parameter to work-around discrepancies between hardware and platform firmware, it's not unusual to see e.g. 38.4MHz listed in _DSD properties as the SoundWire clock source, but the hardware may be based on a 19.2 MHz mclk source.

Add a kernel parameter to work-around discrepancies between hardware
and platform firmware, it's not unusual to see e.g. 38.4MHz listed in
_DSD properties as the SoundWire clock source, but the hardware may be
based on a 19.2 MHz mclk source.

Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
@plbossart
Copy link
Member Author

This is weird

https://sof-ci.01.org/linuxpr/PR5067/build3697/devicetest/index.html?model=LNLM_SDW_AIOC&testcase=multiple-pause-resume-50

2024-06-17 13:31:15 UTC [REMOTE_INFO] pipeline: Amp feedback with arecord
2024-06-17 13:31:15 UTC [REMOTE_INFO] pipeline: Jack In with arecord
2024-06-17 13:31:15 UTC [REMOTE_INFO] Check expect exit status
2024-06-17 13:31:15 UTC [REMOTE_INFO] Amp feedback to command: arecord -D hw:0,3 -r 48000 -c 4 -f S16_LE -vv -i /dev/null -q
spawn arecord -D hw:0,3 -r 48000 -c 4 -f S16_LE -vv -i /dev/null -q
2024-06-17 13:31:15 UTC [REMOTE_INFO] Deepbuffer Jack Out to command: aplay -D hw:0,31 -r 48000 -c 2 -f S16_LE -vv -i /dev/zero -q
arecord: main:831: audio open error: Device or resource busy
2024-06-17 13:31:15 UTC [REMOTE_INFO] wait for expect process finished
spawn aplay -D hw:0,31 -r 48000 -c 2 -f S16_LE -vv -i /dev/zero -q
Hardware PCM card 0 'sof-soundwire' device 31 subdevice 0

First time I see this one @bardliao @fredoh9 @marc-hb

@plbossart
Copy link
Member Author

SOFCI TEST

@bardliao
Copy link
Collaborator

This is weird

https://sof-ci.01.org/linuxpr/PR5067/build3697/devicetest/index.html?model=LNLM_SDW_AIOC&testcase=multiple-pause-resume-50

2024-06-17 13:31:15 UTC [REMOTE_INFO] pipeline: Amp feedback with arecord
2024-06-17 13:31:15 UTC [REMOTE_INFO] pipeline: Jack In with arecord
2024-06-17 13:31:15 UTC [REMOTE_INFO] Check expect exit status
2024-06-17 13:31:15 UTC [REMOTE_INFO] Amp feedback to command: arecord -D hw:0,3 -r 48000 -c 4 -f S16_LE -vv -i /dev/null -q
spawn arecord -D hw:0,3 -r 48000 -c 4 -f S16_LE -vv -i /dev/null -q
2024-06-17 13:31:15 UTC [REMOTE_INFO] Deepbuffer Jack Out to command: aplay -D hw:0,31 -r 48000 -c 2 -f S16_LE -vv -i /dev/zero -q
arecord: main:831: audio open error: Device or resource busy
2024-06-17 13:31:15 UTC [REMOTE_INFO] wait for expect process finished
spawn aplay -D hw:0,31 -r 48000 -c 2 -f S16_LE -vv -i /dev/zero -q
Hardware PCM card 0 'sof-soundwire' device 31 subdevice 0

First time I see this one @bardliao @fredoh9 @marc-hb

But this is not possible caused by this PR, right? We didn't set the parameter in CI devices.

@plbossart
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants