From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Alexander Kaplan <alexander.kaplan@sms-medipool.de>
Cc: "Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Péter Ujfalusi" <peter.ujfalusi@intel.com>,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Takashi Iwai" <tiwai@suse.com>,
linux-sound@vger.kernel.org, "Jaroslav Kysela" <perex@perex.cz>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.dev>,
stable@vger.kernel.org, "Uma Shankar" <uma.shankar@intel.com>
Subject: Re: [PATCH] ALSA: hda/hdmi: disable KAE for Intel Panther Lake
Date: Wed, 1 Jul 2026 01:45:45 +0300 (EEST) [thread overview]
Message-ID: <765b713e-d2a0-6859-2923-53f8e60cb00e@linux.intel.com> (raw)
In-Reply-To: <b6e4caac-53f1-729f-51d2-aa0ca514ab04@linux.intel.com>
Hi,
On Wed, 24 Jun 2026, Kai Vehmanen wrote:
> On Sat, 20 Jun 2026, Alexander Kaplan wrote:
>
[...]
> > So the wedge happens earlier in the sequence, as you suspected, not at
> > the re-arm.
> > The trigger looks like the multichannel DMA start itself once the KAE
> > block has been active in the running power cycle, below the codec verb
> > level.
>
> thanks for the quick test. I'm working with our display folks to test
> this out with some Synaptic DP-alt HDMI converter. This same test
> worked ok with one converter (Lenovo USB-C to HDMI Adapter GX90K37871),
[...]
> I filed a bug to Xe/display to track this effort:
> https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/8412
some progress with this. I attached a work-in-progress patch that fixes
the issue with at least one setup using Club3D CAC-2505 DP-alt HDMI
converter to the bug at:
https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/8412#note_3543741
Needs more work still, but if this approach works, I'll send a proper
patch later to the list.
Br, Kai
next prev parent reply other threads:[~2026-06-30 22:46 UTC|newest]
Thread overview: 11+ 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
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
2026-06-20 15:00 ` Alexander Kaplan
2026-06-24 17:04 ` Kai Vehmanen
2026-06-30 22:45 ` Kai Vehmanen [this message]
2026-07-03 23:24 ` Alexander Kaplan
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=765b713e-d2a0-6859-2923-53f8e60cb00e@linux.intel.com \
--to=kai.vehmanen@linux.intel.com \
--cc=alexander.kaplan@sms-medipool.de \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@intel.com \
--cc=peter.ujfalusi@linux.intel.com \
--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