Skip to content

[BUG] Noisy DMIC recording with concurrent audio playback over speakers #9205

Closed
Closed
[BUG] Noisy DMIC recording with concurrent audio playback over speakers#9205
Assignees
lyakhsingalsu
Labels
P1Blocker bugs or important featuresbugSomething isn't working as expectedproduction blocker

Description

@syedk008
syedk008
opened on Jun 7, 2024

Describe the bug
We observed Noisy DMIC recordings with concurrent playback over speakers on the ARL-S platform.
The issue happens only with 4-channel Dmic recording but not with 2-channels.
To Reproduce
start and stop DMIC recording and playback over speakers using arecord and aplay.

  1. start playback over speakers: aplay -Dhw:0,0 -c 2 -r 48000
  2. start DMIC recording: arecord -Dhw:0,6 -f s32_LE -c 4 -r 48000
  3. wait 10 sec and stop both playback and records
  4. playback recorded file to see if any noise.
    repeat the steps several times.
    you can use the attached script to reproduce the issue.

Reproduction Rate
~25%
Expected behavior
No noise in the recording.

Impact
critical

Environment

  1. kernel: branch: sof-dev and commit:4b0046880585
    sof: v2.9 mtl
  2. Name of the topology file
    • Topology: sof-hda-generic-ace1-4ch.tplg
  3. Name of the platform(s) on which the bug is observed.
    • Platform: ARL-S

concurrent_rec_play_.txt

Activity

  1. syedk008
    added
    bugSomething isn't working as expected
    on Jun 7, 2024
  2. lgirdwood
    added
    P1Blocker bugs or important features
    on Jun 7, 2024
  3. lgirdwood
    added this to the v2.10 milestone on Jun 7, 2024

  4. lgirdwood commented on Jun 7, 2024

    @lgirdwood
    lgirdwood
    on Jun 7, 2024
    Member

    @syedk008 is there any capture WAV file that you can share here ? Does it also matter if capture is started 1st then playback 2nd ?

  5. syedk008 commented on Jun 7, 2024

    @syedk008
    syedk008
    on Jun 7, 2024
    Author

    @lgirdwood attached is the WAV file, rename it to .wav.
    rec.txt
    I could not reproduce the issue when capture starts 1st and playback 2nd. Also the issue always in last two channels 3-4.

  6. lgirdwood
    assigned
    singalsu
    on Jun 10, 2024
  7. lgirdwood
    added
    production blocker
    on Jun 10, 2024

  8. singalsu commented on Jun 10, 2024

    @singalsu
    singalsu
    on Jun 10, 2024
    Collaborator

    Can you please try this pass-through topology version:

    0001-Tools-Topology2-Add-sof-hda-generic-ace1-4ch-48k-pas.patch.gz

  9. singalsu commented on Jun 10, 2024

    @singalsu
    singalsu
    on Jun 10, 2024
    Collaborator

    Please try also this, 2ch with pdm1 (the controller that handles in 4ch channels 3-4):

    0001-Tools-Topology2-Add-topology-sof-hda-generic-ace1-2c.patch.gz

  10. syedk008 commented on Jun 10, 2024

    @syedk008
    syedk008
    on Jun 10, 2024
    Author

    Can you please try this pass-through topology version:

    0001-Tools-Topology2-Add-sof-hda-generic-ace1-4ch-48k-pas.patch.gz

    Issue is reproducible with this topology, but the frequency seems less.

  11. syedk008 commented on Jun 10, 2024

    @syedk008
    syedk008
    on Jun 10, 2024
    Author

    Please try also this, 2ch with pdm1 (the controller that handles in 4ch channels 3-4):

    0001-Tools-Topology2-Add-topology-sof-hda-generic-ace1-2c.patch.gz

    The issue is not reproducible with this topology.

  12. abonislawski commented on Jun 11, 2024

    @abonislawski
    abonislawski
    on Jun 11, 2024
    Member

    @syedk008 could you please attach dmesg log with IPC payload data? (for full iteration - aplay - arecord - end)
    Our validation will try to reproduce exactly the same scenario on ARL-S without linux driver.

    I can confirm it works fine in basic dmic 4ch tests.

  13. syedk008 commented on Jun 11, 2024

    @syedk008
    syedk008
    on Jun 11, 2024
    Author

    @syedk008 could you please attach dmesg log with IPC payload data? (for full iteration - aplay - arecord - end) Our validation will try to reproduce exactly the same scenario on ARL-S without linux driver.

    I can confirm it works fine in basic dmic 4ch tests.

    Attached are the dmesg logs.
    dmesg_clean.txt
    dmesg_noisy.txt

  14. singalsu commented on Jun 12, 2024

    @singalsu
    singalsu
    on Jun 12, 2024
    Collaborator

    I did yesterday testing with the ARL-S device. Some observations:

    • Issues happen with both gcc and xcc builds
    • The DSP load seems to impact occurrence, more frequent corruption with higher load topologies. With DMIC capture in passthough but normal HDA playback pipelines the occurrence is low. Also generally the occurrence varies a lot, sometimes many successive runs are corrupt, sometimes it takes even with full topology a lot of runs to see the issue.
    • Switched DCCOMP off in DMIC blob. Also set capture IIR to passthrough with sof-ctl. When corruption happens, the DC level of corrupted signal shifts the noise to fully to positive PCM codes side.
    • Set in DMIC blob FIR coefficients to zero to force decimator output to zero. Then applied with DC channel registers a fixed offset to channels. With these forced DC values I was never able to see corruption, after some 20 runs of Karim's script. Just clean stream of constant PCM code values, except the start gain ramps. But this needs more runs to confirm this configuration never corripts, so not 100% sure about this.

  15. singalsu commented on Jun 18, 2024

    @singalsu
    singalsu
    on Jun 18, 2024
    Collaborator

    Fix proposal: zephyrproject-rtos/zephyr#74414

  16. kv2019i
    added 2 commits that reference this issue on Jun 20, 2024

    west.yml: update Zephyr to sof/stable-v2.10 0f7a01d360e

    15f8115

    west.yml: update Zephyr to sof/stable-v2.10 0f7a01d360e

    39f76e4
  17. kv2019i
    assigned
    lyakh
    on Jun 25, 2024

  18. lyakh commented on Jun 25, 2024

    @lyakh
    lyakh
    on Jun 25, 2024
    Collaborator

    With zephyrproject-rtos/zephyr#74414 this problem couldn't be reproduced any more so far. Since the noise when it appears with unpatched firmware begins directly at the start of a capture, it makes sense that modifying DMIC initialisation flow fixes the problem.

  19. kv2019i commented on Jun 28, 2024

    @kv2019i
    kv2019i
    on Jun 28, 2024
    Collaborator

    Fixed part of release v2.10 (a Zephyr fix so backported directly), removing the tag. Let's close once the Zephyr fix lands in SOF main via west.yml update (i.e. #9258 or similar).

  20. kv2019i
    removed this from the v2.10 milestone on Jun 28, 2024
  21. kv2019i
    added 2 commits that reference this issue on Jul 3, 2024

    west.ytml: update to Zephyr 650227d8c47f

    7b36d94

    west.ytml: update to Zephyr 650227d8c47f

    d560643

  22. kv2019i commented on Jul 4, 2024

    @kv2019i
    kv2019i
    on Jul 4, 2024
    Collaborator

    Fix merged via #9278

  23. kv2019i
    closed this as completedon Jul 4, 2024
  24. eddy1021
    added a commit that references this issue on Jul 15, 2024

    west.ytml: update to Zephyr 650227d8c47f

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

Metadata

Metadata

Assignees

Labels

P1Blocker bugs or important featuresbugSomething isn't working as expectedproduction blocker

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions