public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Panagiotis Foliadis <pfoliadis@posteo.net>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	Charalampos Mitrodimas <charmitro@posteo.net>
Subject: Re: [PATCH] ALSA: hda/intel: increase default bdl_pos_adj for Nvidia controllers
Date: Wed, 25 Feb 2026 15:58:39 +0100	[thread overview]
Message-ID: <87v7fkdg4g.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260225-nvidia-audio-fix-v1-1-b1383c37ec49@posteo.net>

On Wed, 25 Feb 2026 15:53:43 +0100,
Panagiotis Foliadis wrote:
> 
> The default bdl_pos_adj of 32 for Nvidia HDA controllers is
> insufficient on GA102 (and likely other recent Nvidia GPUs) after S3
> suspend/resume. The controller's DMA timing degrades after resume,
> causing premature IRQ detection in azx_position_ok() which results in
> silent HDMI/DP audio output despite userspace reporting a valid
> playback state and correct ELD data.
> 
> Increase bdl_pos_adj to 64 for AZX_DRIVER_NVIDIA, matching the value
> already used by Intel Apollo Lake for the same class of timing issue.
> 
> Cc: stable@vger.kernel.org
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221069
> Suggested-by: Charalampos Mitrodimas <charmitro@posteo.net>
> Signed-off-by: Panagiotis Foliadis <pfoliadis@posteo.net>

Thanks, applied now.


Takashi

  reply	other threads:[~2026-02-25 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 14:53 [PATCH] ALSA: hda/intel: increase default bdl_pos_adj for Nvidia controllers Panagiotis Foliadis
2026-02-25 14:58 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-25 14:54 Panagiotis Foliadis

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=87v7fkdg4g.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=charmitro@posteo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pfoliadis@posteo.net \
    --cc=stable@vger.kernel.org \
    --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