ASoC: Add q6voice ready for FP5 (on v7.1-kernel)

[wrenix]

adapt #27 for kernel v7.1(.2)

[zstas]

@z3ntu some people confirm that with those patches calls work too on spacewar (nothing phone 1).
do you think we can merge them? it also would be nice to have calls on taoyao

[f-izzo]

Remember that this PR requires to enable SND_SOC_QDSP6_Q6VOICE on the kernel configuration.

[chrisduerr]

The following patch fixes muting of the bottom speaker:
chrisduerr@fb656da

It appears that the following commit, submitted by @valpackett on the mailing list, was changed at some point during development to remove this section (the commit is applied on Luca's kernel):
wrenix@e8ec954

Looking at the mailing list, it seems that Mark Brown commented on removing it initially:
https://lkml.org/lkml/2026/5/19/1926

Then @valpackett said "that doesn't seem required" (not sure if this is in reference to the changes, or the comment from Mark Brown):
https://lkml.org/lkml/2026/5/19/2380

Luca also mentioned that this is causing a warning, but I think he quoted too much text and it doesn't affect this patch (I honestly forget already if I saw any warnings when compiling this):
https://lkml.org/lkml/2026/5/22/1193

I'm curious what Val has to say about this, but to me it seems like it was removed in haste under the assumption that it wasn't necessary to get call audio working. I still can't say whether this specific change is the correct way to get call audio working, but it certainly fixes the issue of the bottom speaker not getting muted for me.

[wrenix]

oh damit, i miss this discussion (and switch to android - lost interesset to fix/work without maintainer Feedback)

[chrisduerr]

lost interesset to fix/work without maintainer Feedback

That's unfortunate to hear, but understandable.

I'm not actually sure why there has been zero feedback at all on either of your set of patches.

[account1009]

I'm also very interested about this part!
Let me know if I can do anything to help finalizing :)

[z3ntu]

Hi @wrenix , it wasn't my intention to make it look like I'm not interested or something.
At least when this voice call work started, there were still plenty of issues that needed to be ironed out and it's still looking like it's moving and not completely ready for integration.
Unfortunately for q6voiced I can't just point you upstream to get feedback since it's a downstream driver (though I'm hoping you're aware of the paid project with postmarketOS that aims to get this functionality finally upstream), but I personally know essentially nothing about the whole subject without first diving into it.
And kernel maintenance on its own for sm6350, sc7280 and milos trees plus any upstreaming and prep work for getting speaker and microphone upstream is still ongoing.
That being said, I really wanted to take a look at this last Friday but got hung up on other topics, but I promise to take a proper look soon and take it for a ride.
Thanks for working on this and sticking with it!

[valpackett]

I'll try to get back to fiddling with aw88261 "soon" but feel free to submit your own patches (to lkml)!

All the code brought in from downstream awinic drivers (everything related to the "firmware" and its profiles) is bad. The convoluted start code path that has this mute thing is related to profile switching. The entire pattern of opaque register-value lists from loaded binaries absolutely stinks and never should've been accepted upstream, when we have datasheets that clearly describe the entire regmap of the hardware… Ideally we'd just expose all the remaining registers (like the whole amplification bypass for earpiece mode) as their own ALSA controls and eliminate all the struct aw_device crap.

BTW the easy hot fix would be to not touch the profile in UCM at all :p

[wrenix]

@z3ntu on the pmaport side, i enable more then on your fp5_defconfig / 6c1c703 : https://gitlab.postmarketos.org/wrenix/pmaports/-/commit/525cb7b33b38925647b0432b930b9d702aaf666d?file_path=device%2Fcommunity%2Flinux-postmarketos-qcom-sc7280%2Fconfig-postmarketos-qcom-sc7280.aarch64#6e42a73c557d269d3b7319942b6b6f6dd1953d8b

[z3ntu]

@wrenix I have seen that, but what's the purpose of all those other options? It was working for me with just CONFIG_SND_SOC_QDSP6_Q6VOICE_DAI & CONFIG_SND_SOC_QDSP6_Q6VOICE and for the other options I'm pretty sure they're not used.

[valpackett]

More specifically, all of those options are 100% for chromebooks (google,sc7280-herobrine… none of those ever publicly shipped, they were cancelled). We use the SM8250 soundcard.