[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <874j182fqd.fsf@oltmanns.dev>
Date: Wed, 05 Feb 2025 23:23:22 +0100
From: Frank Oltmanns <frank@...manns.dev>
To: Johan Hovold <johan@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>, Chris Lew
<quic_clew@...cinc.com>, Stephan Gerhold <stephan.gerhold@...aro.org>,
Johan Hovold <johan+linaro@...nel.org>, Dmitry Baryshkov
<dmitry.baryshkov@...aro.org>, Konrad Dybcio <konradybcio@...nel.org>,
Abel Vesa <abel.vesa@...aro.org>, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, regressions@...ts.linux.dev,
stable@...r.kernel.org, Caleb Connolly <caleb.connolly@...aro.org>, Joel
Selvaraj <joelselvaraj.oss@...il.com>, Alexey Minnekhanov
<alexeymin@...tmarketos.org>
Subject: Re: [PATCH] soc: qcom: mark pd-mapper as broken
On 2025-01-13 at 10:07:15 +0100, Johan Hovold <johan@...nel.org> wrote:
> On Sat, Jan 11, 2025 at 03:21:35PM +0100, Frank Oltmanns wrote:
>> On 2025-01-08 at 15:06:34 +0100, Johan Hovold <johan@...nel.org> wrote:
>
>> > And today I also hit this on the sc8280xp CRD reference design, so as
>> > expected, there is nothing SoC specific about the audio service
>> > regression either:
>> >
>> > [ 11.235564] PDR: avs/audio get domain list txn wait failed: -110
>> > [ 11.241976] PDR: service lookup for avs/audio failed: -110
>> >
>> > even if it may be masked by random changes in timing.
>> >
>> > These means it affects also machines like the X13s which already have
>> > audio enabled.
>>
>> I've blocklisted the in-kernel pd-mapper module for now and have
>> switched back to the userspace pd-mapper.
>>
>> I don't know if it's helpful or not, but I don't get these error logs
>> when using to the in-kernel pd-mapper. It's just that the phone's mic
>> only works on approximately every third boot (unless I defer loading the
>> module).
>
> Ok, then it sounds like you're hitting a separate bug that is also
> triggered by the changed timings with the in-kernel pd-mapper.
I worked on finding out what's causing the issue on sdm845 and I've
submitted a patch here: [1]
> Are there any hints in the logs about what goes wrong in your setup?
Unfortunately not, see [1].
> And
> the speakers are still working, it's just affecting the mic?
Yes, it's only affecting the mic in my setup on xiaomi-beryllium, but
there seem to be issues with the speaker on oneplus-enchilada that can
be fixed with the same approach.
Best regards,
Frank
[1]: https://lore.kernel.org/all/20250205-qcom_pdm_defer-v1-1-a2e9a39ea9b9@oltmanns.dev/
>
> Johan
Powered by blists - more mailing lists