You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug][TGL]Pop noise on I2S max98373 speaker when doing pause/resume test #2255
changed the title [-][Bug][TGL]Pop noise on I2S max98337 speaker when doing pause/resume test [/-][+][Bug][TGL]Pop noise on I2S max98373 speaker when doing pause/resume test [/+]on Jul 8, 2020
update status: I can reproduce this issue. no pop noise is generated with only stream of zero data. And I also check it with SSP loop back, no garbage data is captured. I don't think it is caused by FW for above evidence
if we test start-stop pattern, stream of zero data also produce garbage data at beginning & end. The difference of start-stop pattern and pause-release pattern is that SSP clk is stopped in start-stop case.
I enabled SSP loop back in this case and disable DSM feedback input. The loop back data showed nothing wrong. So the data sent by SSP was correct. It is caused by 98373 only. The pop noise is very slight and user can't notice it in daily usage.
Activity
[-][Bug][TGL]Pop noise on I2S max98337 speaker when doing pause/resume test [/-][+][Bug][TGL]Pop noise on I2S max98373 speaker when doing pause/resume test [/+]RanderWang commentedon Aug 27, 2020
update status: I can reproduce this issue. no pop noise is generated with only stream of zero data. And I also check it with SSP loop back, no garbage data is captured. I don't think it is caused by FW for above evidence
RanderWang commentedon Aug 27, 2020
if we test start-stop pattern, stream of zero data also produce garbage data at beginning & end. The difference of start-stop pattern and pause-release pattern is that SSP clk is stopped in start-stop case.
RanderWang commentedon Aug 31, 2020
I enabled SSP loop back in this case and disable DSM feedback input. The loop back data showed nothing wrong. So the data sent by SSP was correct. It is caused by 98373 only. The pop noise is very slight and user can't notice it in daily usage.