public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Frank Oltmanns <frank@oltmanns.dev>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Chris Lew <quic_clew@quicinc.com>,
	Stephan Gerhold <stephan.gerhold@linaro.org>,
	Johan Hovold <johan+linaro@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abel.vesa@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: mark pd-mapper as broken
Date: Mon, 13 Jan 2025 10:07:15 +0100	[thread overview]
Message-ID: <Z4TXww5rAkMR8OmM@hovoldconsulting.com> (raw)
In-Reply-To: <87wmf18m8g.fsf@oltmanns.dev>

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@kernel.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.

Are there any hints in the logs about what goes wrong in your setup? And
the speakers are still working, it's just affecting the mic?

Johan

  reply	other threads:[~2025-01-13  9:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  7:42 [PATCH] soc: qcom: mark pd-mapper as broken Johan Hovold
2024-10-10  9:55 ` Dmitry Baryshkov
2024-10-10 10:11   ` Johan Hovold
2024-10-10 10:55     ` Dmitry Baryshkov
2024-10-10 11:44       ` Johan Hovold
2024-10-10 11:46         ` neil.armstrong
2024-10-10 13:24           ` Johan Hovold
2024-10-10 13:45             ` Dmitry Baryshkov
2024-10-10 14:07               ` Johan Hovold
2024-10-10 14:13                 ` Dmitry Baryshkov
2024-10-10 14:20                   ` Johan Hovold
2024-10-10 14:42                     ` Dmitry Baryshkov
2024-10-11 10:01 ` Stephan Gerhold
2025-01-06 19:10   ` Frank Oltmanns
2025-01-07 10:02     ` Johan Hovold
2025-01-08 14:06       ` Johan Hovold
2025-01-11 14:21         ` Frank Oltmanns
2025-01-13  9:07           ` Johan Hovold [this message]
2025-02-05 22:23             ` Frank Oltmanns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z4TXww5rAkMR8OmM@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=frank@oltmanns.dev \
    --cc=johan+linaro@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_clew@quicinc.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=stephan.gerhold@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox