From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Icenowy Zheng <uwu@icenowy.me>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH 2/2] ASoC: Intel: Skylake: try to get NHLT blob with PCM params as fallback
Date: Wed, 17 Aug 2022 15:19:50 +0200 [thread overview]
Message-ID: <c3386d45-b643-b4aa-c868-5c113cd2955f@intel.com> (raw)
In-Reply-To: <1891bc72834cb6e25d479c3968c04bcef94c3ad5.camel@icenowy.me>
On 2022-08-17 2:48 PM, Icenowy Zheng wrote:
> 在 2022-08-16星期二的 21:08 +0200,Cezary Rojewski写道:
...
>
> Yes, it's Chell.
>
> BTW do you need other ACPI tables?
At this point, no. Thanks for confirming the platform's name.
>>
>> ..and at this point I probably know more than enough. We have tested
>> basically all of the KBL and AML configurations when fixing
>> regressions
>> during recent skylake-driver up-revs. But Chell (and Lars for that
>> matter) families were not among them as these are based on SKL. I'll
>> follow up on this with our partners and come back here. I'm almost
>> certain topology files for the two families mentioned were not
>> updated
>> along the way.
>
> Could this be an issue of Coreboot, which generates the NHLT table?
NHLT was left alone across all the updates. Updating it is one way of
fixing problems but I don't believe it's necessary in your case.
Topology update is more desirable approach.
> BTW I think Google pinned the official OS of this hardware to a much
> lower kernel version (but I don't want to use the official OS because
> of limited storage of Chell and lack of VM ability of the OS on Chell).
That clarifies things out. Guess the kernel version used there is v4.4
(plus a ton of un-upstreamed patches). Again, will propagate the
information up the chain. Perhaps one of the solutions for end-users
would be providing working UCM files to alsa-topology-conf repo so users
are not powerless in situations such as this one.
Regards,
Czarek
next prev parent reply other threads:[~2022-08-17 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 11:10 [PATCH 1/2] ASoC: Intel: Skylake: fix error message of NHLT blob selection Icenowy Zheng
2022-07-25 11:10 ` [PATCH 2/2] ASoC: Intel: Skylake: try to get NHLT blob with PCM params as fallback Icenowy Zheng
2022-08-02 10:30 ` Cezary Rojewski
2022-08-07 17:26 ` Icenowy Zheng
2022-08-16 19:08 ` Cezary Rojewski
2022-08-17 12:40 ` Mark Brown
2022-08-17 12:48 ` Icenowy Zheng
2022-08-17 13:19 ` Cezary Rojewski [this message]
2022-08-18 9:25 ` Icenowy Zheng
2022-08-18 9:54 ` Cezary Rojewski
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=c3386d45-b643-b4aa-c868-5c113cd2955f@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=uwu@icenowy.me \
--cc=yung-chuan.liao@linux.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