Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	Emil Velikov <emil.velikov@collabora.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Arun Gopal Kondaveeti <arungopal.kondaveeti@amd.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Daniel <dmanlfc@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Sound System <linux-sound@vger.kernel.org>
Subject: Re: Fwd: Steam Deck OLED 6.8.2 nau8821-max fails
Date: Sun, 7 Apr 2024 09:47:00 +0200	[thread overview]
Message-ID: <4d231dc4-0183-47e1-8bfa-3dd225bf8ea3@leemhuis.info> (raw)
In-Reply-To: <ZhFJZoful6nEFskW@archie.me>

On 06.04.24 15:08, Bagas Sanjaya wrote:
> 
> On Bugzilla, Daniel <dmanlfc@gmail.com> reported topology regression
> on Steam Deck OLED [1]. He wrote:

Bagas, why didn't you forward this to me in private first, as we agreed
on as general procedure for cases like this?

Anyway:

>> I'm adding this here, I hope it's the correct place.
>>
>> Currently the Steam Deck OLED fails with Kernel 6.8.2 when trying to initialise the topology for the device.
>> I'm using the `sof-vangogh-nau8821-max.tplg` file from the Steam Deck OLED and associated firmware.
> 
> See Bugzilla for the full thread.
> 
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218677

A quick search made me find these posts/threads that foreshadow the problem:

https://lore.kernel.org/lkml/20231219030728.2431640-1-cristian.ciocaltea@collabora.com/
https://lore.kernel.org/all/a3357e1f-f354-4d4b-9751-6b2182dceea6@amd.com/

From a quick look at the second discussion it seems a bit like we are
screwed, as iiutc topology files are out in the wild for one or the
other approach. So we might have to bite a bullet there and accept the
regression -- but I might easily be totally mistaken here. Would be good
in one of the experts (Venkata Prasad Potturu maybe?) could quickly
explain what's up here.

Ciao, Thorsten

  reply	other threads:[~2024-04-07  7:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06 13:08 Fwd: Steam Deck OLED 6.8.2 nau8821-max fails Bagas Sanjaya
2024-04-07  7:47 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-04-07 10:54   ` Bagas Sanjaya
2024-04-08 23:44   ` Cristian Ciocaltea
2024-04-09  4:44     ` Linux regression tracking (Thorsten Leemhuis)
2024-04-09  7:42       ` Cristian Ciocaltea
2024-04-09  8:04         ` Linux regression tracking (Thorsten Leemhuis)
2024-04-09  8:22           ` Daniel Martin
2024-04-09  8:47           ` Cristian Ciocaltea
2024-04-09  9:19             ` Linux regression tracking (Thorsten Leemhuis)
2024-04-09  9:55               ` Cristian Ciocaltea
2024-04-09 10:57                 ` Daniel Martin
2024-04-09 11:24                   ` Cristian Ciocaltea
     [not found]         ` <CAOyTmd3bpmb7t1fCMKPBXqhVtpdpKRvVq5EA7VXrnb-5Fs9ngQ@mail.gmail.com>
2024-04-09  8:25           ` Cristian Ciocaltea

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=4d231dc4-0183-47e1-8bfa-3dd225bf8ea3@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=arungopal.kondaveeti@amd.com \
    --cc=bagasdotme@gmail.com \
    --cc=broonie@kernel.org \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=dmanlfc@gmail.com \
    --cc=emil.velikov@collabora.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=tiwai@suse.com \
    --cc=venkataprasad.potturu@amd.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