Repository navigation
Conversation
The AOP firmware keeps a device attachment for as long as it runs, and the driver has no way to drop one at removal. When the module is loaded again, the probe's attach calls for the microphone devices get kIOReturnBusy back and the probe fails. The machine then has no audio until it reboots: with the T6040 flow the speaker and jack streams are registered by the same probe and are lost as well. The speaker and jack services already treat that return as attached. Do the same in the probe, and share the constant with aop_spkr. The probe's property writes that follow are accepted by the still attached devices. Signed-off-by: Erik Bourget <erik@ebourget.net>
erikwb
marked this pull request as draft
November 1, 2026 01:35
erikwb
marked this pull request as ready for review
November 1, 2026 02:02
This was referenced Nov 1, 2026
Contributor
Author
|
Superseded by #820, where this is commit 18, unchanged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reloading
snd-soc-aopleaves the machine without audio until a reboot. This makes the probe accept a device that is still attached from the previous load.What happens
The AOP firmware keeps a device attachment for as long as it runs, and the driver has no call to drop one at removal. On the next load, the probe attaches the microphone devices again (
pdm0,hpai,lpai, andlilbwhere there's an HF decimator). The firmware answers kIOReturnBusy (0xe00002d5), the probe fails with "Unable to attach device", and every card the driver provides stays missing. With the T6040 flow that includes the speakers and the jack, which the same probe registers.The speaker and jack services already treat that return as "attached" (
Service::getinaop_spkr.rs). This does the same in the probe'saudio_attach_device, with a debug message, and movesAUDIO_RET_BUSYintoaop_audio.rssoaop_spkrshares it.aop_t8140keeps its own copy, as it does for the rest of its protocol constants.Testing (J713)
This was tested on a J713 kernel with #439's T8132 support, where the AOP audio node binds
apple,t8132-aop-audio/apple,t6041-aop-audioand takes this probe.rmmod snd_soc_aopand theninsmodfail the probe on thepdm0attach, and there's no audio until a reboot.snd-soc-aop(withsnd-soc-macaudio), the last two with the final version of this commit. After each one:--strictis clean;sound/soc/applebuilds with W=1 and no warnings;Image, modules and dtbs on integration/aurora with no new warnings.