在 2022-08-16星期二的 21:08 +0200，Cezary Rojewski写道： > On 2022-08-07 7:26 PM, Icenowy Zheng wrote: > > 在 2022-08-02星期二的 12:30 +0200，Cezary Rojewski写道： > > > On 2022-07-25 1:10 PM, Icenowy Zheng wrote: > > > > Switching to use pipeline parameters to get NHLT blob breaks > > > > audio > > > > on > > > > HP Chromebook 13 G1 (at least with MrChromeBox firmware). > > ... > > > > Could you share the NHLT file from your platform plus the format > > > used > > > by > > > the cras/userspace tool? Did you try playing over simple aplay > > > tool > > > instead? > > > > I tried 48000Hz 2ch 32bit with speaker-test. > > > > Attached is /sys/firmware/acpi/tables/NHLT. > > > Thanks for the NHLT dump. Total of five endpoints are part of the > description: > > id 0, DMIC capture, formats: > [0] 2/16/16/48000 > [1] 2/32/32/48000 > id 1, I2S SSP0 playback, formats: > [0] 2/24/32/48000 > id 2, I2S SSP0 capture, formats: > [0] 4/32/32/48000 > id 3, I2S SSP1 playback, formats: > [0] 2/24/32/48000 > id 4, I2S SSP1 capture, formats: > [0] 2/24/32/48000 > > I know not what "speaker-test" means. Could you specify which > endpoint Well to be honest I know nearly nothing about Intel ASoC. (In fact I have only a little experience dealing with ASoC on DT-based platforms with asoc-simple-card) I assume it uses the first playback stream, because I didn't explicitly choose any streams; and speaker-test is only a playback test program. > you are speaking of? Providing either alsa info or at least output of > 'lsmod | grep snd' would help. I'd like to be aware of which machine > board are we talking about. > > What could be guessed with the current info (and some google query), > is > that we are dealing with SKL-Y m5-6Y57, codenamed 'Chell' and the > speaker-test is playing through an I2S codec connected to SSP0 port. > It's probably max98357a. The skylake-driver version you have gets > confused with 24/32 format (userspace is probably attempting 32/32). > That or topology file is incorrect.. Yes, it's Chell. BTW do you need other ACPI tables? > > ..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? 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). > > > Regards, > Czarek
