Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Alexander Kaplan <alexander.kaplan@sms-medipool.de>,
	Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org
Cc: Jaroslav Kysela <perex@perex.cz>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	stable@vger.kernel.org, "Shankar, Uma" <uma.shankar@intel.com>
Subject: Re: [PATCH] ALSA: hda/hdmi: disable KAE for Intel Panther Lake
Date: Thu, 11 Jun 2026 12:33:50 +0300	[thread overview]
Message-ID: <ec0d51a0-a31d-4c06-92f6-e38c408884b9@linux.intel.com> (raw)
In-Reply-To: <5e05e954-338c-4a87-8a60-1fd2bd6bb8ce@linux.intel.com>



On 11/06/2026 12:08, Péter Ujfalusi wrote:
> My setup is: laptop HDMI -> SYNIC HDMI audio extractor -> HDMI KVM ->
> monitor w/o speakers.
> I use the extractor to grab the audio and it is clean every time I play
> audio to HDMI.

Just to rule out iffy equipment on my side, I have connected the PTL
laptop to my Denon AVR both in SOF and legacy HDA mode. I cannot hear
any issue regarding to audio on my 5.1 speaker set.

> Can this be somehow related to the DP-to-HDMI converter? Have you tested
> that with other machine?
> Or a combination of xe2+DP-to-HDMI?
> 
> Ccing Uma for display side
>> This may also fix the silent Dolby TrueHD passthrough on Battlemage
>> reported in
>> https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/7515.
>> Battlemage uses the same keep-alive code path and TrueHD passthrough
>> is the same first-multichannel-stream pattern, but I could not test
>> that hardware.
>>
>> Workaround for affected systems without this patch:
>> snd_hda_codec_intelhdmi.enable_silent_stream=0.
>>
>>  sound/hda/codecs/hdmi/intelhdmi.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/sound/hda/codecs/hdmi/intelhdmi.c b/sound/hda/codecs/hdmi/intelhdmi.c
>> index 6a7882544a..52997caae9 100644
>> --- a/sound/hda/codecs/hdmi/intelhdmi.c
>> +++ b/sound/hda/codecs/hdmi/intelhdmi.c
>> @@ -791,7 +791,7 @@ static const struct hda_device_id snd_hda_id_intelhdmi[] = {
>>  	HDA_CODEC_ID_MODEL(0x8086281e, "Battlemage HDMI",	MODEL_ADLP),
>>  	HDA_CODEC_ID_MODEL(0x8086281f, "Raptor Lake P HDMI",	MODEL_ADLP),
>>  	HDA_CODEC_ID_MODEL(0x80862820, "Lunar Lake HDMI",	MODEL_ADLP),
>> -	HDA_CODEC_ID_MODEL(0x80862822, "Panther Lake HDMI",	MODEL_ADLP),
>> +	HDA_CODEC_ID_MODEL(0x80862822, "Panther Lake HDMI",	MODEL_TGL),
>>  	HDA_CODEC_ID_MODEL(0x80862823, "Wildcat Lake HDMI",	MODEL_ADLP),
>>  	HDA_CODEC_ID_MODEL(0x80862824, "Nova Lake HDMI",	MODEL_ADLP),
>>  	HDA_CODEC_ID_MODEL(0x80862882, "Valleyview2 HDMI",	MODEL_BYT),
> 

-- 
Péter


  reply	other threads:[~2026-06-11  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 17:48 [PATCH] ALSA: hda/hdmi: disable KAE for Intel Panther Lake Alexander Kaplan
2026-06-11  9:08 ` Péter Ujfalusi
2026-06-11  9:33   ` Péter Ujfalusi [this message]
2026-06-11 14:44     ` Alexander Kaplan
2026-06-12 12:45       ` Péter Ujfalusi
2026-06-12 18:13         ` Alexander Kaplan
2026-06-16 19:13           ` Kai Vehmanen

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=ec0d51a0-a31d-4c06-92f6-e38c408884b9@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=alexander.kaplan@sms-medipool.de \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=uma.shankar@intel.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