From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexey Klimov <alexey.klimov@linaro.org>,
Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: codecs: lpass-wsa-macro: Fix speaker quality distortion
Date: Thu, 11 Sep 2025 08:23:20 +0200 [thread overview]
Message-ID: <a52f809d-c8ae-411a-b305-46fd4233e2a0@linaro.org> (raw)
In-Reply-To: <DCPKY2GED44G.I2DSV6ZBXYAQ@linaro.org>
On 11/09/2025 03:29, Alexey Klimov wrote:
> On Sun Aug 31, 2025 at 4:14 PM BST, Krzysztof Kozlowski wrote:
>> After removal of first AIF_INVALID DAI identifier, this kcontrol was
>> updating wrong entries in active channel count and mask arrays which was
>> visible in reduced quality (distortions) during speaker playback on
>> several boards like Lenovo T14s laptop and Qualcomm SM8550-based boards.
>>
>> Reported-by: Alexey Klimov <alexey.klimov@linaro.org>
>> Fixes: bb4a0f497bc1 ("ASoC: codecs: lpass: Drop unused AIF_INVALID first DAI identifier")
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
>>
>> Reported via IRC.
>> Fix for current v6.17-RC cycle.
>>
>> I will be investigating rest of lpass macro codecs a bit later.
>
> Any updates on other lpass macro codecs? Is something still broken there
> or are they fine? So I guess the changes for wsa and rx macro were applied.
> va, tx?
The remaining two - VA and TX - are fine, I checked them.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-09-11 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 15:14 [PATCH] ASoC: codecs: lpass-wsa-macro: Fix speaker quality distortion Krzysztof Kozlowski
2025-09-04 7:24 ` Srinivas Kandagatla
2025-09-04 18:31 ` Mark Brown
2025-09-11 1:29 ` Alexey Klimov
2025-09-11 6:23 ` Krzysztof Kozlowski [this message]
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=a52f809d-c8ae-411a-b305-46fd4233e2a0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexey.klimov@linaro.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srini@kernel.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