From: Steven Kendall <skend@chromium.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/cs8409: Fix for Dell Cirrus audio jack detect
Date: Fri, 17 Jul 2026 17:18:36 -0400 [thread overview]
Message-ID: <CAB1bpFA5m_H2-9ksFvFNyXdrAirE+W3VaLuyRDX8Ncv4-V-dKQ@mail.gmail.com> (raw)
In-Reply-To: <87se5ky9re.wl-tiwai@suse.de>
> Have you tried to turn off the runtime PM for HD-audio?
> The question is whether the unsol event doesn't work *at all*, or it
> just stops when the codec (or the controller) is powered down.
> Also, CS8409 driver enables the per-node power-save feature, and this
> might influence, too.
I tried this before (disabling power management) and didn't see any
success and just tried it two ways now:
adding a segment in sound/hda/controllers/intel.c like
@@ -2306,6 +2306,8 @@ static const struct snd_pci_quirk
power_save_denylist[] = {
SND_PCI_QUIRK(0x1028, 0x0962, "Dell ALC3271", 0),
/* https://bugzilla.kernel.org/show_bug.cgi?id=220210 */
SND_PCI_QUIRK(0x17aa, 0x5079, "Lenovo Thinkpad E15", 0),
+ /* Dell CS8409 Warlock MLK */
+ SND_PCI_QUIRK(0x1028, 0x0bb2, "Dell CS8409 Warlock MLK", 0),
{}
};
and adding a segment in sound/hda/codecs/cirrus/cs8409.c like
@@ -1606,6 +1607,13 @@ static int cs8409_probe(struct hda_codec
*codec, const struct hda_device_id *id)
}
snd_hda_apply_fixup(codec, HDA_FIXUP_ACT_PROBE);
+
+ if (codec->bus->pci->subsystem_vendor == 0x1028 &&
+ codec->bus->pci->subsystem_device == 0x0bb2) {
+ pm_runtime_get_noresume(&codec->core.dev);
+ pm_runtime_forbid(&codec->core.dev);
+ }
+
return 0;
}
I debug logs showing both these firing and
/sys/module/snd_hda_intel/parameters/power_save reads as 0. However
with either or both of these changes applied the plug events are still
not detected on first boot, and the "fix" of closing the lid and
opening it again still restores jack detection on Chrome OS.
next prev parent reply other threads:[~2026-07-17 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 21:21 Steven 'Steve' Kendall
2026-07-14 5:50 ` Takashi Iwai
2026-07-14 19:51 ` Steven Kendall
2026-07-15 7:47 ` Takashi Iwai
2026-07-17 21:18 ` Steven Kendall [this message]
2026-07-14 16:17 ` Stefan Binding
2026-07-14 19:26 ` Steven Kendall
2026-07-15 15:16 ` Stefan Binding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB1bpFA5m_H2-9ksFvFNyXdrAirE+W3VaLuyRDX8Ncv4-V-dKQ@mail.gmail.com \
--to=skend@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox