From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Jason Montleon <jmontleo@redhat.com>
Cc: "Sasa Ostrouska" <casaxa@gmail.com>,
"Linux regressions mailing list" <regressions@lists.linux.dev>,
"Greg KH" <gregkh@linuxfoundation.org>,
lma@semihalf.com,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
stable@vger.kernel.org, "Takashi Iwai" <tiwai@suse.de>,
"amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Tue, 31 Jan 2023 16:46:06 +0100 [thread overview]
Message-ID: <48c07209-0704-e134-cf7b-629ba34cbe7c@intel.com> (raw)
In-Reply-To: <CAJD_bP+Te5a=OfjN9YrjGOG2PzudQ87=5FEKj6YLFxfKyFe5bw@mail.gmail.com>
On 2023-01-31 4:16 PM, Jason Montleon wrote:
> Maybe this is the problem.
>
> I think most of us are pulling the topology and firmware from the
> chromeos recovery images for lack of any other known source, and it
> looks a little different than this. Those can be downloaded like so:
> https://gist.github.com/jmontleon/8899cb83138f2653f520fbbcc5b830a0
>
> After placing the topology file you'll see these errors and audio will
> not work until they're also copied in place.
> snd_soc_skl 0000:00:1f.3: Direct firmware load for
> dsp_lib_dsm_core_spt_release.bin failed with error -2
> snd_soc_skl 0000:00:1f.3: Direct firmware load for
> intel/dsp_fw_C75061F3-F2B2-4DCC-8F9F-82ABB4131E66.bin failed with
> error -2
>
> Once those were in place, up to 6.0.18 audio worked.
>
> Is there a better source for the topology file?
There was no other source for the topology files for a very long time.
This has been quite recently changed with the introduction of avsdk [1]
and avs-topology-xml [2] repos. These hold 2 major branches each:
1) main - for the avs-driver which has already replaced the
skylake-driver in client department and shall soon do the same in the
remaining areas
2) for-skylake-driver - for the skylake-driver, help downstream in
dealing with bugs and ease the transition to the avs-driver
Updated AudioDSP firmware binaries should be shared soon, completing
last few remaining steps. Not every library can be shared though. And
can't comment on usage of 3rd party loadable modules outside of
supported set of configurations.
[1]: https://github.com/thesofproject/avsdk
[2]: https://github.com/thesofproject/avs-topology-xml
Kind regards,
Czarek
next prev parent reply other threads:[~2023-01-31 15:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 17:09 Google Pixelbook EVE, no sound in kernel 6.1.x Jason Montleon
2023-01-28 17:52 ` Greg KH
2023-01-29 0:23 ` Jason Montleon
2023-01-30 6:33 ` Jason Montleon
2023-01-30 11:27 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-30 12:15 ` Cezary Rojewski
2023-01-30 12:22 ` Sasa Ostrouska
2023-01-31 12:36 ` Cezary Rojewski
2023-01-31 14:58 ` Sasa Ostrouska
2023-01-31 15:48 ` Cezary Rojewski
2023-01-31 16:02 ` Sasa Ostrouska
2023-01-31 15:16 ` Jason Montleon
2023-01-31 15:46 ` Cezary Rojewski [this message]
2023-02-01 11:05 ` Amadeusz Sławiński
2023-02-01 14:33 ` Jason Montleon
2023-02-04 15:16 ` Jason Montleon
2023-02-06 9:03 ` Amadeusz Sławiński
2023-02-06 13:51 ` Jason Montleon
2023-02-06 19:57 ` Jason Montleon
2023-02-06 21:15 ` Sasa Ostrouska
2023-02-09 16:13 ` Jason Montleon
2023-02-09 19:22 ` Jason Montleon
2023-02-10 13:09 ` Cezary Rojewski
2023-02-10 14:56 ` Jason Montleon
2023-02-10 17:15 ` Sasa Ostrouska
2023-01-30 11:23 ` Linux kernel regression tracking (#update)
-- strict thread matches above, loose matches on Subject: below --
2023-01-23 20:44 Sasa Ostrouska
2023-01-24 5:09 ` Greg KH
2023-01-24 10:18 ` Lukasz Majczak
2023-01-24 11:34 ` Sasa Ostrouska
2023-01-24 12:11 ` Lukasz Majczak
2023-01-24 14:31 ` Sasa Ostrouska
2023-01-24 21:38 ` Sasa Ostrouska
2023-01-25 15:48 ` Lukasz Majczak
2023-01-24 11:30 ` Sasa Ostrouska
2023-01-26 12:59 ` Linux kernel regression tracking (#adding)
2023-01-27 10:06 ` Sasa Ostrouska
2023-02-09 14:11 ` Sasa Ostrouska
2023-02-24 1:10 ` Sasa Ostrouska
2023-02-24 20:43 ` Sasa Ostrouska
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=48c07209-0704-e134-cf7b-629ba34cbe7c@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=casaxa@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmontleo@redhat.com \
--cc=lma@semihalf.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).