Bug 219276 - Realtek audio driver takes 170ms longer to resume from S2idle on Dell machines
Summary: Realtek audio driver takes 170ms longer to resume from S2idle on Dell machines
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks: 178231
  Show dependency tree
 
Reported: 2024-09-13 23:44 UTC by Todd Brandt
Modified: 2024-09-14 00:25 UTC (History)
1 user (show)

See Also:
Kernel Version: v6.11-rc6
Subsystem:
Regression: Yes
Bisected commit-id: 9b82ff1362f50914c8292902e07be98a9f59d33d


Attachments
otcpl-dell-7386-whl_freeze-6.11-rc5.html (683.13 KB, text/html)
2024-09-13 23:44 UTC, Todd Brandt
Details
otcpl-dell-7386-whl_freeze-6.11-rc6.html (687.00 KB, text/html)
2024-09-13 23:45 UTC, Todd Brandt
Details

Description Todd Brandt 2024-09-13 23:44:53 UTC
Created attachment 306876 [details]
otcpl-dell-7386-whl_freeze-6.11-rc5.html

Three of our systems take approximately 170ms longer in resume since 6.11.0-rc6. The otcpl-dell-7386-whl, otcpl-dell-latitude-5420-tgl, and otcpl-dell-9360-kbl. The patch seems to include an msleep which is usually not a good sign. Please see if there some other way to guarantee headset sound other than putting in a mandatory msleep as we want to keep resume as fast as possible.

commit 9b82ff1362f50914c8292902e07be98a9f59d33d
Author: Kailang Yang <kailang@realtek.com>
Date:   Thu Aug 22 10:54:19 2024 +0800

    ALSA: hda/realtek - Fixed ALC256 headphone no sound
    
    Dell platform, plug headphone or headset, it had a chance to get no
    sound from headphone.
    Replace depop procedure will solve this issue.
    
    Signed-off-by: Kailang Yang <kailang@realtek.com>
    Link: https://lore.kernel.org/bb8e2de30d294dc287944efa0667685a@realtek.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
Comment 1 Todd Brandt 2024-09-13 23:45:25 UTC
Created attachment 306877 [details]
otcpl-dell-7386-whl_freeze-6.11-rc6.html
Comment 2 Todd Brandt 2024-09-13 23:46:09 UTC
The dmesg logs are in the attached html files, click the dmesg button in the upper right. The hardware data is all included in the log file, click the log button in the upper right.
Comment 3 Todd Brandt 2024-09-14 00:25:20 UTC
I just removed this one patch and built against upstream just to confirm it's the culprit, it is.

Note You need to log in before you can comment on or make changes to this bug.