From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Daniel Martin <dmanlfc@gmail.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Arun Gopal Kondaveeti <arungopal.kondaveeti@amd.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Sound System <linux-sound@vger.kernel.org>
Subject: Re: Fwd: Steam Deck OLED 6.8.2 nau8821-max fails
Date: Tue, 9 Apr 2024 11:25:31 +0300 [thread overview]
Message-ID: <bf713024-a96b-457a-9281-0406e6eb0828@collabora.com> (raw)
In-Reply-To: <CAOyTmd3bpmb7t1fCMKPBXqhVtpdpKRvVq5EA7VXrnb-5Fs9ngQ@mail.gmail.com>
On 4/9/24 10:54 AM, Daniel Martin wrote:
> Why this was changed in the first place could do with some explaining,
> as Valve had this implemented first in the SteamDeck (probably collabora
> dev).
> There were no other implementations out in the wild AFAIK & now with the
> 6.8.x kernel, this issue has manifested because of an enum change.
The OLED model was launched with a 6.1-based kernel which relied on a
downstream implementation of the Vangogh SOF drivers. Those were
mainlined by AMD way later, in v6.6, but during the upstreaming process
we ended up with this unfortunate ID assignments incompatibility.
> I cannot for the life of me find an alternative topology file. Where are
> the other implementations? Therefore it makes sense aligning to what was
> done before on the Steam Deck OLED.
I'm not aware of an alternative topology file available so far.
> Alternatively, if Valve could provide an updated topology file for 6.8+
> kernels, that would be great too.
> Just my two cents from a humble OS dev, trying to make stuff work.
I think that would be the long-term goal, so until that is figured out,
the easiest workaround to get this working with mainline is to apply the
enum change patch.
Regards,
Cristian
prev parent reply other threads:[~2024-04-09 8:25 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)
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 [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=bf713024-a96b-457a-9281-0406e6eb0828@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=arungopal.kondaveeti@amd.com \
--cc=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=dmanlfc@gmail.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