Skip to content

[BUG][TGL]Wov trigger volume is different with format s16_le/24_le/32_le. #3112

Closed

Description

@YvonneYang2

Describe the bug
When set wov capture volume under 60, wov can barely be triggered with format s16_le.
set volume under 30, wov can barely be triggered with format s24_le.
At the same time, wov with format s32_le is so easy to be triggered even no need to make some obvious noise.

To Reproduce

  1. Boot up system
  2. Set capture volume "PGA9.0 9" 50
  3. Run wov test with format 16_le/24_le/32_le via command "arecord -Dhw:0,100 -M -N -f s32_le -r 16000 -i -vvv -c2 --buffer-size=80000 ./tmp.wav"
  4. Turn down the "PGA9.0 9" to 30 and repeat step 3.
  5. Turn down the "PGA9.0 9" to 20 and repeat step 3.

Reproduce rate
5/5

Expected result
wov with format s16/s24/s32 can be triggered.

Actual result
When set wov capture volume under 60, wov can barely be triggered with format s16_le.
set volume under 30, wov can barely be triggered with format s24_le.
At the same time, wov with format s32_le is so easy to be triggered even no need to make some obvious noise.

Environment
Kernel:https://github.com/thesofproject/linux/commits/topic/sof-dev (commit: 1b2f260)

FW:
https://github.com/thesofproject/sof/tree/releases/tgl/v7.0-rc5 commit: 1dd07a8

TPLG:sof-tgl-max98373-rt5682.tplg
Platform:Chromebook with codec 98373 in I2S mode.

sof-trace.log
dmesg.log

Activity

  1. added
    bugSomething isn't working as expected
    TGLApplies to Tiger Lake
    on Jun 30, 2020
  2. changed the title [-][BUG][TGL]It's hard to trigger wov when set volume under 30 with format 16_le/24_le but s32_le can be auto triggered.[/-] [+][BUG][TGL]Wov trigger volume is different with format s16_le/24_le/32_le.[/+] on Jun 30, 2020
  3. tlauda commented on Jun 30, 2020

    @tlauda
    Contributor

    @YvonneYang2 Is it a regression?

  4. ClarexZhou commented on Jun 30, 2020

    @ClarexZhou

    This isn't a regression, always behavior like this.

  5. keyonjie commented on Jun 30, 2020

    @keyonjie
    Contributor

    Hi @tlauda @ClarexZhou I just root caused and will provide a PR to fix this soon, so you can not put effort to it atm.

  6. keyonjie commented on Jun 30, 2020

    @keyonjie
    Contributor

    PR #3116 is submitted to fix the issue here.

  7. ClarexZhou commented on Jun 30, 2020

    @ClarexZhou

    Verified, error not seen with PR #3116

  8. keyonjie commented on Jul 8, 2020

    @keyonjie
    Contributor

    Close it as #3116 was merged.

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

Metadata

Metadata

Assignees

Labels

Fix confirmedFix for the issue has been found and verifiedKeyword DetectionApplies to Keyword DetectionP1Blocker bugs or important featuresTGLApplies to Tiger LakebugSomething isn't working as expected

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions