Re: [PATCH 2/2] ASoC: Intel: Skylake: try to get NHLT blob with PCM params as fallback

Icenowy Zheng
2022-08-18T09:26:39Z

在 2022-08-17星期三的 15:19 +0200，Cezary Rojewski写道：
> 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 how could I fix the topology?

I now use topology files from GalliumOS (which, I assume, is extracted
from ChromeOS).

>
> > 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