From: Takashi Iwai <tiwai@suse.de>
To: "\"Nícolas F. R. A. Prado\"" <nfraprado@collabora.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
kernel@collabora.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: Force resume if acomp notified during system suspend
Date: Mon, 29 Jun 2026 12:39:24 +0200 [thread overview]
Message-ID: <87wlvhpr4z.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260626-hda-force-resume-eld-notify-v1-1-a92cb01393e0@collabora.com>
On Fri, 26 Jun 2026 17:47:22 +0200,
Nícolas F. R. A. Prado wrote:
>
> Currently if an HDMI cable is connected while the system is suspended,
> the HDMI audio jack status stays off after resume.
>
> This is due to the jack state not being synced by the HDA HDMI codec
> device's runtime resume, as that never happens if the device was runtime
> suspended before the system suspended, or by the acomp notification
> triggered from the DRM side if that happens before the HDA HDMI codec
> device has resumed.
>
> To fix this, if snd_hda_hdmi_acomp_pin_eld_notify() gets called before
> the HDA HDMI codec device has resumed, mark it to be forcefully runtime
> resumed at the next PM complete time.
>
> Do this using a separate acomp_requested_resume flag that can be
> temporarily set without overwriting forced_resume for drivers that
> always want to force resume.
>
> Assisted-by: Copilot:claude-sonnet-4.6
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Applied to for-next branch now. Thanks.
Takashi
prev parent reply other threads:[~2026-06-29 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 15:47 [PATCH] ALSA: hda: Force resume if acomp notified during system suspend Nícolas F. R. A. Prado
2026-06-29 10:39 ` Takashi Iwai [this message]
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=87wlvhpr4z.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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