From: Johan Hovold <johan@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
krzysztof.kozlowski@linaro.org, linux-sound@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
dmitry.baryshkov@linaro.org, johan+linaro@kernel.org
Subject: Re: [PATCH v3 0/6] ASoC: q6apm: fix under runs and fragment sizes
Date: Wed, 5 Mar 2025 10:06:52 +0100 [thread overview]
Message-ID: <Z8gULECJ463Ilv2p@hovoldconsulting.com> (raw)
In-Reply-To: <Z8c2OVRp8af1K1D1@hovoldconsulting.com>
On Tue, Mar 04, 2025 at 06:19:53PM +0100, Johan Hovold wrote:
> On Tue, Mar 04, 2025 at 05:12:20PM +0000, Srinivas Kandagatla wrote:
> > On 04/03/2025 17:04, Johan Hovold wrote:
>
> > > Unfortunately, this series still regresses Pulseaudio as capture is now
> > > choppy (e.g. when recording using parecord).
> > >
> > > During our off-list debugging sessions you suggested reducing the max
> > > capture period size (that this series increases) to 6144 (same as min)
> > > and that fixed the Pulseaudio capture issue. In v3 the, the max period
> > > is again increased to 65536 which appears to break Pulseaudio capture.
> >
> > I have verified pulseaudio on my side as well, the 64 byte alignment
> > should have fixed the issue on the pulseaudio side.
> >
> > Did you pick up the [PATCH v3 4/6] ASoC: qdsp6: q6apm-dai: set correct
> > period and buffer alignment. patch in your tests?
>
> Yes, I'm running with the full series applied. I tested PA on the X13s
> (and PW on the T14s).
I just tested PA on the T14s and it has the same problem with
choppy recording with this series applied.
As with the (amended) v2, setting the max capture period size to 6144
appears to make the problem go away.
Johan
next prev parent reply other threads:[~2025-03-05 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:57 [PATCH v3 0/6] ASoC: q6apm: fix under runs and fragment sizes srinivas.kandagatla
2025-03-04 10:57 ` [PATCH v3 1/6] ASoC: q6apm-dai: schedule all available frames to avoid dsp under-runs srinivas.kandagatla
2025-03-04 10:57 ` [PATCH v3 2/6] ASoC: q6apm: add q6apm_get_hw_pointer helper srinivas.kandagatla
2025-03-04 10:57 ` [PATCH v3 3/6] ASoC: q6apm-dai: make use of q6apm_get_hw_pointer srinivas.kandagatla
2025-03-04 10:57 ` [PATCH v3 4/6] ASoC: qdsp6: q6apm-dai: set correct period and buffer alignment srinivas.kandagatla
2025-03-04 10:57 ` [PATCH v3 5/6] ASoC: qdsp6: q6apm-dai: fix capture pipeline overruns srinivas.kandagatla
2025-03-04 10:57 ` [PATCH v3 6/6] ASoC: qdsp6: q6apm-dai: fix playback dsp pipeline underruns srinivas.kandagatla
2025-03-04 17:04 ` [PATCH v3 0/6] ASoC: q6apm: fix under runs and fragment sizes Johan Hovold
2025-03-04 17:12 ` Srinivas Kandagatla
2025-03-04 17:19 ` Johan Hovold
2025-03-05 9:06 ` Johan Hovold [this message]
2025-03-05 9:21 ` Johan Hovold
2025-03-05 22:17 ` Caleb Connolly
2025-03-06 13:15 ` Srinivas Kandagatla
2025-03-06 17:04 ` Dmitry Baryshkov
2025-03-06 13:56 ` Krzysztof Kozlowski
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=Z8gULECJ463Ilv2p@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
/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