* ASoC: rt5677: Do not apply Yoga Book ACPI GPIO mappings to Samus
@ 2026-11-16 21:24 Ted Vera
2026-11-17 8:11 ` Pierre-Louis Bossart
0 siblings, 1 reply; 2+ messages in thread
From: Ted Vera @ 2026-11-16 21:24 UTC (permalink / raw)
To: linux-sound; +Cc: regressions, oder_chiou, lgirdwood, broonie
Summary:
On a Google Pixel 2 LS Chromebook (Samus, EVT2) running Fedora 45
kernel 7.3.3-300.fc45.x86_64, the RT5677 codec repeatedly fails probe
with Failed to request POW_LDO2: -517 (-EPROBE_DEFER). The codec
appears in devices_deferred, no RT5677 ALSA card is registered, and
only HDMI audio is available.
The driver’s ACPI GPIO mapping added by commit 0cc00de3dd5b maps GPIO
resource indexes 0 and 1 to reset and pow-ldo2 for every ACPI RT5677
device. Samus’s DSDT uses those resources for codec GPIOs (jack detect
and mic-present), not Yoga Book-style external reset and power GPIOs.
The driver requests the mapped GPIOs before registering the codec’s
GPIO chip, which appears to cause the deferred-probe loop.
Test and result:
I built a temporary module against the matching Fedora kernel source
that skips devm_acpi_dev_add_driver_gpios() on DMI board Samus. With
that module, the RT5677 device bound successfully, the bdw-rt5677 ALSA
card appeared, and laptop-speaker audio worked. Secure Boot remained
enabled. This strongly supports the ACPI GPIO mapping as the cause.
Suggested fix: Restrict the mapping to devices whose ACPI GPIO
resource layout matches the Yoga Book, rather than applying it to
every RT5677 ACPI device.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ASoC: rt5677: Do not apply Yoga Book ACPI GPIO mappings to Samus
2026-11-16 21:24 ASoC: rt5677: Do not apply Yoga Book ACPI GPIO mappings to Samus Ted Vera
@ 2026-11-17 8:11 ` Pierre-Louis Bossart
0 siblings, 0 replies; 2+ messages in thread
From: Pierre-Louis Bossart @ 2026-11-17 8:11 UTC (permalink / raw)
To: Ted Vera, linux-sound
Cc: regressions, oder_chiou, lgirdwood, broonie, Andy Shevchenko
On 11/16/26 22:24, Ted Vera wrote:
> Summary:
> On a Google Pixel 2 LS Chromebook (Samus, EVT2) running Fedora 45
> kernel 7.3.3-300.fc45.x86_64, the RT5677 codec repeatedly fails probe
> with Failed to request POW_LDO2: -517 (-EPROBE_DEFER). The codec
> appears in devices_deferred, no RT5677 ALSA card is registered, and
> only HDMI audio is available.
>
> The driver’s ACPI GPIO mapping added by commit 0cc00de3dd5b maps GPIO
> resource indexes 0 and 1 to reset and pow-ldo2 for every ACPI RT5677
> device. Samus’s DSDT uses those resources for codec GPIOs (jack detect
> and mic-present), not Yoga Book-style external reset and power GPIOs.
> The driver requests the mapped GPIOs before registering the codec’s
> GPIO chip, which appears to cause the deferred-probe loop.
>
> Test and result:
> I built a temporary module against the matching Fedora kernel source
> that skips devm_acpi_dev_add_driver_gpios() on DMI board Samus. With
> that module, the RT5677 device bound successfully, the bdw-rt5677 ALSA
> card appeared, and laptop-speaker audio worked. Secure Boot remained
> enabled. This strongly supports the ACPI GPIO mapping as the cause.
>
> Suggested fix: Restrict the mapping to devices whose ACPI GPIO
> resource layout matches the Yoga Book, rather than applying it to
> every RT5677 ACPI device.
Humm, it's a 2015 device that I used in the past without issues. It was
one of the early SOF devices... See commit bcb43fd.
Is this a commercial version or an early prototype? I don't recall what
EVT2 stands for in Chromebooks.
Also adding Andy in Cc:, he was the one who suggested the GPIO fixes.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-17 8:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-16 21:24 ASoC: rt5677: Do not apply Yoga Book ACPI GPIO mappings to Samus Ted Vera
2026-11-17 8:11 ` Pierre-Louis Bossart
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox